 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| intel ? 82801BA i/o controller hub 2 (ich2) and intel ? 82801BAm i/o controller hub 2 mobile (ich2-m) datasheet october 2000 order number: 290687-002
82801BA ich2 and 82801BAm ich2-m datasheet information in this document is provided in connection with intel products. no license, express or implied, by estoppel or othe rwise, to any intellectual property rights is granted by this document. except as provided in intel's terms and conditions of sale for such products, inte l assumes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel products including liabil ity or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property righ t. intel products are not intended for use in medical, life saving, or life sustaining applications. intel may make changes to specifications and product descriptions at any time, without notice. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. the intel 82801BA i/o controller hub 2 (ich2) and intel 82801BAm i/o controller hub 2 (ich2-m) may contain design defects or er rors known as errata which may cause the product to deviate from published specifications. current characterized errata are available on req uest. i 2 c is a two-wire communications bus/protocol developed by philips. smbus is a subset of the i 2 c bus/protocol and was developed by intel. implementations of the i 2 c bus/protocol or the smbus bus/protocol may require licenses from various entities, including philips electronics n.v. and north american philips corporation. alert on lan and wake on lan are results of the ibm/intel advanced manageability alliance and are trademarks of ibm corporation . copies of documents which have an ordering number and are referenced in this document, or other intel literature may be obtaine d by: calling 1-800-548-4725 or by visiting intel's website at http://www.intel.com. copyright ? intel corporation, 2000 *third-party brands and names are the property of their respective owners. 82801BA ich2 and 82801BAm ich2-m datasheet iii intel ? 82801BA/m ich2/ich2-m features pci bus i/f ? supports pci at 33 mhz ? supports pci rev 2.2 specification ? 133 mbyte/sec maximum throughput ? supports up to 6 master devices on pci ? one pci req/gnt pair can be given higher arbitration priority (intended for external 1394 host controller) integrated lan controller ? wfm 2.0 compliant ? interface to discrete lan connect component ? 10/100 mbit/sec ethernet support ? 1 mbit/sec homepna* support integrated ide controller ? independent timing of up to 4 drives ? ultra ata/100/66/33, bmide and pio modes ? read transfers up to 100mb/s, writes to 89 mb/s ? separate ide connections for primary and secondary cables ? implements write ping-pong buffer for faster write performance usb ? 2 uhci host controllers with a total of 4 ports ?usb 1.1 compliant ? supports wake-up from sleeping states s1?s4 ? supports legacy keyboard/mouse software ac'97 link for audio and telephony codecs ? ac?97 2.1 compliant ? independent bus master logic for 5 channels (pcm in/out, mic input, modem in/out) ? separate independent pci functions for audio and modem ? support for up to six channels of pcm audio output (full ac3 decode) ? supports wake-up events interrupt controller ? support up to 8 pci interrupt pins ? supports pci 2.2 message-based interrupts ? two cascaded 82c59 ? integrated i/o apic capability ? 15 interrupts supported in 8259 mode, 24 supported in i/o apic mode ? supports serial interrupt protocol ? supports front-side bus interrupt delivery 1.8 v operation with 3.3 v i/o ? 5v tolerant buffers on ide, pci, usb over- current and legacy signals gpio ? ttl, open-drain, inversion timers based on 82c54 ? system timer, refresh request, speaker tone output power management logic ? acpi 1.0 compliant ? acpi power management timer ? pci pme# support ? smi# generation ? all registers readable/restorable for proper resume from 0v suspend states ? support for apm-based legacy power management for non-acpi implementations external glue integration ? integrated pull-up, pull-down and series termination resistors on ide and processor interface enhanced hub i/f buffers improve routing flexibility (not available with all memory controller hubs) firmware hub (fwh) i/f supports bios memory size up to 8 mbs low pin count (lpc) i/f ? allows connection of legacy isa and x-bus devices such as super i/o ? supports two master/dma devices. enhanced dma controller ? two cascaded 8237 dma controllers ? pci dma: supports pc/pci ? includes two pc/pci req#/gnt# pairs ? supports lpc dma ? supports dma collection buffer to provide type-f dma performance for all dma channels real-time clock ? 256-byte battery-backed cmos ram ? hardware implementation to indicate century rollover system tco reduction circuits ? timers to generate smi# and reset upon detection of system hang ? timers to detect improper processor reset ? integrated processor frequency strap logic sm bus ? host interface allows processor to communicate via sm bus ? slave interface allows an external microcontroller to access system resources ? compatible with most 2-wire components that are also i 2 c compatible supports isa bus via external pci-isa bridge 360-pin ebga package ? tri-state modes to enable mobile swap bay (82801BAm ich2-m) ? acpi-defined power states - c1?c2, s3?s5 (82801BA ich2) - c1?c3, s1, s3?s5 (82801BAm ich2-m) ? support for ?intel ? speedstep? technology? processor power control (82801BAm ich2-m) ? pci clkrun# support (82801BAm ich2-m) the intel ? 82801BA ich2 and 82801BAm ich2-m may contain design defects or errors known as errata which may cause the products to deviate from published specifications. current characterized errata are available on request. shading,as is shown here, indicates differences between the two components. iv 82801BA ich2 and 82801BAm ich2-m datasheet intel ? 82801BA (ich2) and 82801BAm (ich2-m) simplified block diagram intruder# smlink[1:0] hl11:0] hl_stb hl_stb# hlcomp thrm# slp_s3 slp_s5# pwrok pwrbtn# ri# rsmrst# sus_stat# /lpcpd# susclk rsm_pwrok (ich2) or lan_pwrok (ich2-m) vrmpwrgd ad[31:0] c/be[3:0]# devsel# frame# irdy# trdy# stop# par perr# req[0:4]# req5#/reqb# /gpio1 reqa#/ gpio0 gnt[0:4]# gnt5#/gntb# /gpio17 gnta#/ gpio16 pciclk pcirst# plock# serr# pme# interrupt blk_ich2-ich2m a20m# cpuslp# ferr# ignne# init# intr nmi smi# stpclk# rcin# a20gate cpupwrgd processor interface pci interface usb serirq pirq[a:d]# pirq[h:e]/ gpio[5:2] irq[14:15] apicclk apicd[1:0] usbp1p usbp1n usbp0p usbp0n oc[3:0]# rtcx1 rtcx2 clk14 clk48 clk66 rtc clocks misc. signals spkr rtcrst# (ich2) tp0 fs0 pdcs1# sdcs1# pdcs3# sdcs3# pda[2:0] sda[2:0] pdd[15:0] sdd[15:0] pddreq sddreq pddack# sddack# pdior# sdior# pdiow# sdiow# piordy siordy ide interface hub interface lpc interface smbus interface power mgnt. ac_rst# ac_sync ac_bit_clk ac_sdout ac_sdin0 ac_sdin1 ac'97 link firmware hub system mgnt. general purpose i/o fwh[3:0] /lad[3:0] fwh[4] /lframe# lad[3:0] /fwh[4] lframe# /fwh[4] ldrq[0:1]# smbdata smbclk smbalert# /gpio[11] lan_clk lan_rxd[2:0] lan_txd[2:0] lan_rstsync system mgnt. system mgnt. ee_shclk ee_din ee_dout ee_cs (ich2-m)clkrun# / vgate (ich2-m) slp_s1# (ich2-m) c3_stat#/gpio[21] (ich2-m) agpbusy# (ich2-m) stp_pci# (ich2-m) stp_cpu# (ich2-m) batlow# (ich2-m) cpuperf# (ich2-m) ssmuxsel (ich2-m) note: 1. the gpio signals listed above represent the gpio signals for the 82801BA ich2. some of these signals are not implemented in the 82801BAm ich2-m. see signal description chapter for details. gpio[13:11,8:6,4:3,1:0] gpio[23:16] gpio[28:24] 82801BA ich2 and 82801BAm ich2-m datasheet v system configuration main memory processor pci bus pci slots host controller i/o controller hub 2 82801BA (ich2) and 82801BAm (ich2-m) fwh 4xusb gpio isa bridge (optional) super i/o (required) lpc i/f graphics controller smbus device(s) smbus ac'97 codec(s) (optional) ac'97 2.1 ata/100/66/33 4 ide drives hub interface pci agent lan controller moon2 docking bridge (optional) (ich2-m) vi 82801BA ich2 and 82801BAm ich2-m datasheet contents 1 introduction ................................................................................................................1- 1 1.1 about this document ....................................................................................1-1 1.2 overview.......................................................................................................1-3 2 signal description......................................................................................................2-1 2.1 hub interface to host controller ...................................................................2-1 2.2 link to lan connect.....................................................................................2-1 2.3 eeprom interface .......................................................................................2-2 2.4 firmware hub interface ................................................................................2-2 2.5 pci interface.................................................................................................2-2 2.6 ide interface.................................................................................................2-5 2.7 lpc interface................................................................................................2-6 2.8 interrupt interface .........................................................................................2-6 2.9 usb interface ...............................................................................................2-7 2.10 power management interface.......................................................................2-7 2.11 processor interface.......................................................................................2-9 2.12 smbus interface .........................................................................................2-10 2.13 system management interface...................................................................2-10 2.14 real time clock interface ..........................................................................2-11 2.15 other clocks ...............................................................................................2-11 2.16 miscellaneous signals ................................................................................2-11 2.17 ac?97 link ..................................................................................................2-12 2.18 general purpose i/o...................................................................................2-12 2.19 power and ground......................................................................................2-13 2.20 pin straps ...................................................................................................2-14 2.20.1 functional straps ...........................................................................2-14 2.20.2 test signals ...................................................................................2-15 2.20.2.1 test mode selection.......................................................2-15 2.20.2.2 test straps (82801BA ich2 only) ..................................2-15 2.20.3 external rtc circuitry ...................................................................2-16 2.20.4 v5ref / vcc3_3 sequencing requirements .................................2-16 3 power planes and pin states ....................................................................................3-1 3.1 power planes................................................................................................3-1 3.2 integrated pull-ups and pull-downs.............................................................3-1 3.3 ide integrated series termination resistors ...............................................3-2 3.4 output and i/o signals planes and states ...................................................3-2 3.5 power planes for input signals.....................................................................3-6 4 system clock domains..............................................................................................4-1 82801BA ich2 and 82801BAm ich2-m datasheet vii 5 functional description ...............................................................................................5-1 5.1 hub interface to pci bridge (d30:f0)...........................................................5-1 5.1.1 pci bus interface.............................................................................5-1 5.1.2 pci-to-pci bridge model .................................................................5-2 5.1.3 idsel to device number mapping ..................................................5-2 5.1.4 serr# functionality........................................................................5-2 5.1.5 parity error detection.......................................................................5-4 5.1.6 standard pci bus configuration mechanism ..................................5-5 5.1.7 pci dual address cycle (dac) support (82801BA ich2 only) .......................................................................5-6 5.2 lan controller (b1:d8:f0)............................................................................5-6 5.2.1 lan controller architectural overview ............................................5-7 5.2.2 lan controller pci bus interface ....................................................5-9 5.2.2.1 bus slave operation.........................................................5-9 5.2.2.2 bus master operation.....................................................5-10 5.2.3 clockrun# signal (82801BAm ich2-m only)............................5-13 5.2.3.1 pci power management ................................................5-13 5.2.3.2 pci reset signal ............................................................5-15 5.2.3.3 wake-up events .............................................................5-15 5.2.3.4 wake on lan (preboot wake-up) ..................................5-16 5.2.4 serial eeprom interface ..............................................................5-17 5.2.5 csma/cd unit ...............................................................................5-19 5.2.6 media management interface ........................................................5-20 5.2.7 tco functionality ..........................................................................5-20 5.3 lpc bridge (w/ system and management functions) (d31:f0).................5-20 5.3.1 lpc interface .................................................................................5-21 5.3.1.1 lpc cycle types............................................................5-21 5.3.1.2 start field definition .......................................................5-22 5.3.1.3 cycle type / direction (cyctype + dir)......................5-22 5.3.1.4 size.................................................................................5-22 5.3.1.5 sync..............................................................................5-23 5.3.1.6 sync time-out ..............................................................5-23 5.3.1.7 sync error indication ....................................................5-23 5.3.1.8 lframe# usage............................................................5-24 5.3.1.9 i/o cycles .......................................................................5-25 5.3.1.10 bus master cycles..........................................................5-25 5.3.1.11 lpc power management ...............................................5-25 5.3.1.12 configuration and ich2 implications ..............................5-25 5.4 dma operation (d31:f0) ............................................................................5-26 5.4.1 channel priority .............................................................................5-26 5.4.2 address compatibility mode ..........................................................5-27 5.4.3 summary of dma transfer sizes ..................................................5-27 5.4.4 autoinitialize...................................................................................5-28 5.4.5 software commands .....................................................................5-29 5.5 pci dma .....................................................................................................5-30 5.5.1 pci dma expansion protocol ........................................................5-30 5.5.2 pci dma expansion cycles ..........................................................5-32 5.5.3 dma addresses .............................................................................5-32 5.5.4 dma data generation....................................................................5-32 5.5.5 dma byte enable generation........................................................5-33 5.5.6 dma cycle termination .................................................................5-33 5.5.7 lpc dma .......................................................................................5-33 viii 82801BA ich2 and 82801BAm ich2-m datasheet 5.5.8 asserting dma requests...............................................................5-33 5.5.9 abandoning dma requests ..........................................................5-34 5.5.10 general flow of dma transfers ....................................................5-35 5.5.11 terminal count ..............................................................................5-35 5.5.12 verify mode....................................................................................5-35 5.5.13 dma request deassertion ............................................................5-36 5.5.14 sync field / ldrq# rules ...........................................................5-37 5.6 8254 timers (d31:f0).................................................................................5-38 5.6.1 timer programming .......................................................................5-38 5.6.2 reading from the interval timer ....................................................5-39 5.7 8259 interrupt controllers (pic) (d31:f0) ..................................................5-41 5.7.1 interrupt handling ..........................................................................5-42 5.7.1.1 generating interrupts .....................................................5-42 5.7.1.2 acknowledging interrupts ...............................................5-42 5.7.1.3 hardware/software interrupt sequence .........................5-43 5.7.2 initialization command words (icwx) ...........................................5-43 5.7.3 operation command words (ocw) ..............................................5-44 5.7.4 modes of operation .......................................................................5-45 5.7.5 masking interrupts .........................................................................5-47 5.7.6 steering pci interrupts ..................................................................5-47 5.8 advanced interrupt controller (apic) (d31:f0) ..........................................5-48 5.8.1 interrupt handling ..........................................................................5-48 5.8.2 interrupt mapping...........................................................................5-49 5.8.3 apic bus functional description...................................................5-50 5.8.3.1 physical characteristics of apic....................................5-50 5.8.3.2 apic bus arbitration ......................................................5-50 5.8.3.3 bus message formats ...................................................5-51 5.8.4 pci message-based interrupts......................................................5-56 5.8.4.1 theory of operation .......................................................5-56 5.8.4.2 registers and bits associated with pci interrupt delivery ..........................................................................5-56 5.8.5 front-side interrupt delivery..........................................................5-57 5.8.5.1 theory of operation .......................................................5-57 5.8.5.2 edge-triggered operation..............................................5-57 5.8.5.3 level-triggered operation .............................................5-57 5.8.5.4 registers associated with front-side bus interrupt delivery ..........................................................................5-58 5.8.5.5 interrupt message format ..............................................5-58 5.9 serial interrupt (d31:f0) .............................................................................5-60 5.9.1 start frame....................................................................................5-60 5.9.2 data frames ..................................................................................5-60 5.9.3 stop frame ....................................................................................5-61 5.9.4 specific interrupts not supported via serirq ..............................5-61 5.9.5 data frame format .......................................................................5-62 5.10 real time clock (d31:f0) ..........................................................................5-63 5.10.1 update cycles ...............................................................................5-63 5.10.2 interrupts........................................................................................5-64 5.10.3 lockable ram ranges ..................................................................5-64 5.10.4 century rollover ............................................................................5-64 5.10.5 clearing battery-backed rtc ram...............................................5-64 82801BA ich2 and 82801BAm ich2-m datasheet ix 5.11 processor interface (d31:f0)......................................................................5-66 5.11.1 processor interface signals ...........................................................5-66 5.11.1.1 a20m# ............................................................................5-66 5.11.1.2 init#...............................................................................5-66 5.11.1.3 ferr#/ignne# (coprocessor error).............................5-67 5.11.1.4 nmi .................................................................................5-67 5.11.1.5 stpclk# and cpuslp# signals ..................................5-68 5.11.1.6 cpupwrgood signal..................................................5-68 5.11.2 dual processor issues (82801BA ich2 only) ................................5-68 5.11.2.1 signal differences (82801BA ich2 only) .......................5-68 5.11.2.2 power management (82801BA ich2 only) ....................5-68 5.11.3 speed strapping for processor......................................................5-69 5.12 power management (d31:f0).....................................................................5-71 5.12.1 ich2 and system power states ....................................................5-72 5.12.2 system power planes....................................................................5-74 5.12.3 ich2 power planes........................................................................5-74 5.12.4 smi#/sci generation.....................................................................5-74 5.12.5 dynamic processor clock control .................................................5-77 5.12.5.1 throttling using stpclk# .............................................5-78 5.12.5.2 transition rules among s0/cx and throttling states ....5-78 5.12.6 dynamic pci clock control (82801BAm ich2-m) .........................5-79 5.12.6.1 conditions for stopping the pci clock (82801BAm ich2-m) ......................................................5-79 5.12.6.2 conditions for maintaining the pci clock (82801BAm ich2-m) ......................................................5-79 5.12.6.3 conditions for stopping the pci clock (82801BAm ich2-m) ......................................................5-79 5.12.6.4 conditions for re-starting the pci clock (82801BAm ich2-m) ......................................................5-80 5.12.6.5 other causes of clkrun# going active (82801BAm ich2-m) ......................................................5-80 5.12.6.6 lpc devices and clkrun# (82801BAm ich2-m) .......5-80 5.12.7 sleep states...................................................................................5-81 5.12.7.1 initiating sleep state.......................................................5-81 5.12.7.2 exiting sleep states .......................................................5-81 5.12.7.3 sx?g3?sx, handling power failures .............................5-83 5.12.8 thermal management....................................................................5-84 5.12.8.1 thrm# signal ................................................................5-84 5.12.8.2 thrm# initiated passive cooling...................................5-84 5.12.8.3 thrm# override software bit ........................................5-84 5.12.8.4 processor-initiated passive cooling (via programmed duty cycle on stpclk#)..................5-85 5.12.8.5 active cooling.................................................................5-85 5.12.9 intel ? speedstep? technology protocol (82801BAm ich2-m only)..............................................................5-85 5.12.9.1 intel ? speedstep? technology processor requirements (82801BAm ich2-m)...............................5-86 5.12.9.2 intel ? speedstep? technology states (82801BAm ich2-m) ......................................................5-86 5.12.9.3 voltage regulator interface (82801BAm ich2-m) .........5-87 x 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.10 event input signals and their usage ............................................5-87 5.12.10.1 pwrbtn# ? power button...........................................5-87 5.12.10.2 ri# ? ring indicate .......................................................5-88 5.12.10.3 pme# ? pci power management event.......................5-88 5.12.10.4 agpbusy# (82801BAm ich2-m) .................................5-88 5.12.11 alt access mode ............................................................................5-89 5.12.11.1 write only registers with read paths in alternate access mode ..................................................5-89 5.12.11.2 pic reserved bits ..........................................................5-91 5.12.11.3 read only registers with write paths in alternate access mode ..................................................5-91 5.12.12 system power supplies, planes, and signals ...............................5-91 5.12.13 clock generators ...........................................................................5-93 5.12.13.1 clock control signals from ich2-m to clock synthesizer (82801BAm ich2-m only) ..........................5-93 5.12.14 legacy power management theory of operation .........................5-94 5.12.14.1 desktop apm power management (82801BA ich2 only) .....................................................5-94 5.12.14.2 mobile apm power management (82801BAm ich2-m only) ..............................................5-94 5.13 system management (d31:f0)...................................................................5-95 5.13.1 theory of operation.......................................................................5-95 5.13.2 alert on lan* .................................................................................5-96 5.14 general purpose i/o...................................................................................5-98 5.15 ide controller (d31:f1) ..............................................................................5-99 5.15.1 pio transfers ................................................................................5-99 5.15.2 bus master function ....................................................................5-101 5.15.3 ultra ata/33 protocol ..................................................................5-105 5.15.4 ultra ata/66 protocol ..................................................................5-107 5.15.5 ultra ata/100 protocol ................................................................5-107 5.15.6 ultra ata/33/66/100 timing ........................................................5-107 5.15.7 mobile ide swap bay (82801BAm ich2-m only) ........................5-107 5.16 usb controller (device 31:functions 2 and 4) .........................................5-108 5.16.1 data structures in main memory .................................................5-108 5.16.1.1 frame list pointer ........................................................5-108 5.16.1.2 transfer descriptor (td) ..............................................5-109 5.16.1.3 queue head (qh) ........................................................5-113 5.16.2 data transfers to/from main memory........................................5-114 5.16.2.1 executing the schedule................................................5-114 5.16.2.2 processing transfer descriptors ..................................5-114 5.16.2.3 command register, status register, and td status bit interaction ....................................................5-115 5.16.2.4 transfer queuing .........................................................5-116 5.16.3 data encoding and bit stuffing....................................................5-119 5.16.4 bus protocol ................................................................................5-120 5.16.4.1 bit ordering ..................................................................5-120 5.16.4.2 sync field...................................................................5-120 5.16.4.3 packet field formats ...................................................5-120 5.16.4.4 address fields..............................................................5-121 5.16.4.5 frame number field ....................................................5-122 5.16.4.6 data field .....................................................................5-122 5.16.4.7 cyclic redundancy check (crc) ................................5-122 82801BA ich2 and 82801BAm ich2-m datasheet xi 5.16.5 packet formats............................................................................5-123 5.16.5.1 token packets..............................................................5-123 5.16.5.2 start of frame packets.................................................5-123 5.16.5.3 data packets ................................................................5-124 5.16.5.4 handshake packets......................................................5-124 5.16.5.5 handshake responses ................................................5-125 5.16.6 usb interrupts .............................................................................5-125 5.16.6.1 transaction based interrupts .......................................5-125 5.16.6.2 non-transaction based interrupts................................5-127 5.16.7 usb power management ............................................................5-127 5.16.8 usb legacy keyboard operation................................................5-128 5.17 smbus controller functional description (d31:f3) ..................................5-130 5.17.1 host controller .............................................................................5-130 5.17.1.1 command protocols .....................................................5-131 5.17.1.2 i 2 c behavior .................................................................5-136 5.17.1.3 heartbeat for use with the external lan controller ....5-136 5.17.2 bus arbitration .............................................................................5-137 5.17.3 interrupts / smi# ..........................................................................5-137 5.17.4 smbalert#................................................................................5-138 5.17.5 smbus slave interface ................................................................5-138 5.18 ac?97 controller functional description (audio d31:f5, modem d31:f6)5-142 5.18.1 ac-link overview .........................................................................5-143 5.18.2 ac-link low power mode ...........................................................5-151 5.18.3 ac?97 cold reset ........................................................................5-152 5.18.4 ac?97 warm reset ......................................................................5-152 5.18.5 system reset...............................................................................5-153 5.19 firmware hub interface ............................................................................5-154 5.19.1 field definitions ...........................................................................5-154 5.19.2 protocol........................................................................................5-155 6 register and memory mapping..................................................................................6-1 6.1 pci devices and functions...........................................................................6-1 6.2 pci configuration map..................................................................................6-2 6.3 i/o map .........................................................................................................6-2 6.3.1 fixed i/o address ranges...............................................................6-3 6.3.2 variable i/o decode ranges ...........................................................6-5 6.4 memory map .................................................................................................6-6 6.4.1 boot-block update scheme.............................................................6-7 7 lan controller registers (b1:d8:f0).........................................................................7-1 7.1 pci configuration registers (b1:d8:f0).......................................................7-1 7.1.1 vid?vendor id register (lan controller?b1:d8:f0) ...................7-2 7.1.2 did?device id register (lan controller?b1:d8:f0) ...................7-2 7.1.3 pcicmd?pci command register (lan controller?b1:d8:f0) ............................................................7-2 7.1.4 pcists?pci status register (lan controller?b1:d8:f0) ...........7-3 7.1.5 revid?revision id register (lan controller?b1:d8:f0) ............7-3 7.1.6 scc?sub-class code register (lan controller?b1:d8:f0) ............................................................7-4 7.1.7 bcc?base-class code register (lan controller?b1:d8:f0) ............................................................7-4 7.1.8 cls?cache line size register (lan controller?b1:d8:f0) ........7-4 xii 82801BA ich2 and 82801BAm ich2-m datasheet 7.1.9 pmlt?pci master latency timer register (lan controller?b1:d8:f0) ............................................................7-4 7.1.10 headtyp?header type register (lan controller?b1:d8:f0) ............................................................7-5 7.1.11 csr_mem_base csr?memory-mapped base address register (lan controller?b1:d8:f0)..............................................7-5 7.1.12 csr_io_base?csr i/o-mapped base address register (lan controller?b1:d8:f0) ............................................................7-5 7.1.13 svid?subsystem vendor id (lan controller?b1:d8:f0) ............7-6 7.1.14 sid?subsystem id (lan controller?b1:d8:f0) ...........................7-6 7.1.15 cap_ptr?capabilities pointer (lan controller?b1:d8:f0) ........7-6 7.1.16 int_ln?interrupt line register (lan controller?b1:d8:f0)........7-7 7.1.17 int_pn?interrupt pin register (lan controller?b1:d8:f0).........7-7 7.1.18 min_gnt?minimum grant register (lan controller?b1:d8:f0) ............................................................7-7 7.1.19 max_lat?maximum latency register (lan controller?b1:d8:f0) ............................................................7-7 7.1.20 cap_id?capability id register (lan controller?b1:d8:f0)........7-8 7.1.21 nxt_ptr?next item pointer (lan controller?b1:d8:f0) ...........7-8 7.1.22 pm_cap?power management capabilities (lan controller?b1:d8:f0) ............................................................7-8 7.1.23 pmcsr?power management control/status register (lan controller?b1:d8:f0) ............................................................7-9 7.1.24 data?data register (lan controller?b1:d8:f0) ........................7-9 7.2 lan control / status registers (csr) ........................................................7-10 7.2.1 system control block status word register .................................7-11 7.2.2 system control block command word register ...........................7-12 7.2.3 system control block general pointer register ............................7-14 7.2.4 port register ..............................................................................7-14 7.2.5 eeprom control register ............................................................7-15 7.2.6 management data interface (mdi) control register .....................7-16 7.2.7 receive dma byte count register................................................7-16 7.2.8 early receive interrupt register ....................................................7-17 7.2.9 flow control register ....................................................................7-18 7.2.10 power management driver (pmdr) register................................7-19 7.2.11 general control register ...............................................................7-19 7.2.12 general status register ................................................................7-20 7.2.13 statistical counters ........................................................................7-20 8 hub interface to pci bridge registers (d30:f0) .......................................................8-1 8.1 pci configuration registers (d30:f0) ..........................................................8-1 8.1.1 vid?vendor id register (hub-pci?d30:f0) ...............................8-2 8.1.2 did?device id register (hub-pci?d30:f0)................................8-2 8.1.3 cmd?command register (hub-pci?d30:f0).............................8-3 8.1.4 pd_sts?primary device status register (hub-pci?d30:f0) ........................................................................8-4 8.1.5 revid?revision id register (hub-pci?d30:f0) ........................8-4 8.1.6 scc?sub-class code register (hub-pci?d30:f0)....................8-5 8.1.7 bcc?base-class code register (hub-pci?d30:f0)..................8-5 8.1.8 pmlt?primary master latency timer register (hub-pci?d30:f0) ........................................................................8-5 8.1.9 headtyp?header type register (hub-pci?d30:f0)................8-5 82801BA ich2 and 82801BAm ich2-m datasheet xiii 8.1.10 pbus_num?primary bus number register (hub-pci?d30:f0) ........................................................................8-6 8.1.11 sbus_num?secondary bus number register (hub-pci?d30:f0) ........................................................................8-6 8.1.12 sub_bus_num?subordinate bus number register (hub-pci?d30:f0) ........................................................................8-6 8.1.13 smlt?secondary master latency timer register (hub-pci?d30:f0) ........................................................................8-6 8.1.14 iobase?i/o base register (hub-pci?d30:f0) ..........................8-7 8.1.15 iolim?i/o limit register (hub-pci?d30:f0) ..............................8-7 8.1.16 secsts?secondary status register (hub-pci?d30:f0)...........8-8 8.1.17 membase?memory base register (hub-pci?d30:f0) .............8-9 8.1.18 memlim?memory limit register (hub-pci?d30:f0) .................8-9 8.1.19 pref_mem_base?prefetchable memory base register (hub-pci?d30:f0) ........................................................................8-9 8.1.20 pref_mem_mlt?prefetchable memory limit register (hub-pci?d30:f0) ......................................................................8-10 8.1.21 iobase_hi?i/o base upper 16 bits register (hub-pci?d30:f0) ......................................................................8-10 8.1.22 iolim_hi?i/o limit upper 16 bits register (hub-pci?d30:f0) ......................................................................8-10 8.1.23 int_line?interrupt line register (hub-pci?d30:f0) ..............8-10 8.1.24 bridge_cnt?bridge control register (hub-pci?d30:f0) .....8-11 8.1.25 bridge_cnt2?bridge control register 2 (hub-pci?d30:f0) ......................................................................8-11 8.1.26 cnf?ich2 configuration register (hub-pci?d30:f0) .............8-12 8.1.27 mtt?multi-transaction timer register (hub-pci?d30:f0) ......8-12 8.1.28 pci_mast_sts?pci master status register (hub-pci?d30:f0) ......................................................................8-13 8.1.29 err_cmd?error command register (hub-pci?d30:f0) ........8-13 8.1.30 err_sts?error status register (hub-pci?d30:f0)................8-14 9 lpc interface bridge registers (d31:f0) ..................................................................9-1 9.1 pci configuration registers (d31:f0) ..........................................................9-1 9.1.1 vid?vendor id register (lpc i/f?d31:f0) ..................................9-2 9.1.2 did?device id register (lpc i/f?d31:f0) ..................................9-2 9.1.3 pcicmd?pci command register (lpc i/f?d31:f0) ................9-3 9.1.4 pcists?pci device status (lpc i/f?d31:f0) ............................9-4 9.1.5 revid?revision id register (lpc i/f?d31:f0)...........................9-4 9.1.6 pi?programming interface (lpc i/f?d31:f0) ..............................9-5 9.1.7 scc?sub-class code register (lpc i/f?d31:f0) ......................9-5 9.1.8 bcc?base-class code register (lpc i/f?d31:f0) ....................9-5 9.1.9 headtyp?header type register (lpc i/f?d31:f0) ..................9-5 9.1.10 pmbase?acpi base address (lpc i/f?d31:f0)........................9-6 9.1.11 acpi_cntl?acpi control (lpc i/f?d31:f0)..............................9-6 9.1.12 bios_cntl (lpc i/f?d31:f0) ......................................................9-7 9.1.13 tco_cntl?tco control (lpc i/f?d31:f0) ...............................9-7 9.1.14 gpiobase?gpio base address (lpc i/f?d31:f0) ...................9-8 9.1.15 gpio_cntl?gpio control (lpc i/f?d31:f0) ............................9-8 9.1.16 pirq[n]_rout?pirq[a,b,c,d] routing control (lpc i/f?d31:f0) ...........................................................................9-8 9.1.17 serirq_cntl?serial irq control (lpc i/f?d31:f0) ................9-9 xiv 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.18 pirq[n]_rout?pirq[e,f,g,h] routing control (lpc i/f?d31:f0) ...........................................................................9-9 9.1.19 d31_err_cfg?device 31 error configuration register (lpc i/f?d31:f0) .........................................................................9-10 9.1.20 d31_err_sts?device 31 error status register (lpc i/f?d31:f0) .........................................................................9-10 9.1.21 pci_dma_cfg?pci dma configuration (lpc i/f?d31:f0) .....9-11 9.1.22 gen_cntl?general control register (lpc i/f?d31:f0) .........9-11 9.1.23 gen_sts?general status (lpc i/f?d31:f0)............................9-13 9.1.24 rtc_conf?rtc configuration register (lpc i/f?d31:f0).....9-14 9.1.25 com_dec?lpc i/f communication port decode ranges (lpc i/f?d31:f0) .........................................................................9-14 9.1.26 fdd/lpt_dec?lpc i/f fdd & lpt decode ranges (lpc i/f?d31:f0) .........................................................................9-15 9.1.27 snd_dec?lpc i/f sound decode ranges (lpc i/f?d31:f0) .........................................................................9-15 9.1.28 fwh_dec_en1?fwh decode enable 1 register (lpc i/f?d31:f0) .........................................................................9-16 9.1.29 gen1_dec?lpc i/f generic decode range 1 (lpc i/f?d31:f0) .........................................................................9-17 9.1.30 lpc_en?lpc i/f enables (lpc i/f?d31:f0) ............................9-17 9.1.31 fwh_sel1?fwh select 1 register (lpc i/f?d31:f0).............9-19 9.1.32 gen2_dec?lpc i/f generic decode range 2 (lpc i/f?d31:f0) .........................................................................9-20 9.1.33 fwh_sel2?fwh select 2 register (lpc i/f?d31:f0).............9-20 9.1.34 fwh_dec_en2?fwh decode enable 2 register (lpc i/f?d31:f0) .........................................................................9-21 9.1.35 func_dis?function disable register (lpc i/f?d31:f0) .........9-22 9.2 dma i/o registers......................................................................................9-23 9.2.1 dmabase_ca?dma base and current address registers .......9-24 9.2.2 dmabase_cc?dma base and current count registers...........9-25 9.2.3 dmamem_lp?dma memory low page registers .....................9-25 9.2.4 dmacmd?dma command register ...........................................9-26 9.2.5 dmasts?dma status register...................................................9-26 9.2.6 dma_wrsmsk?dma write single mask register.....................9-27 9.2.7 dmach_mode?dma channel mode register...........................9-27 9.2.8 dma clear byte pointer register ..................................................9-28 9.2.9 dma master clear register ...........................................................9-28 9.2.10 dma_clmsk?dma clear mask register ...................................9-28 9.2.11 dma_wrmsk?dma write all mask register .............................9-29 9.3 timer i/o registers.....................................................................................9-30 9.3.1 tcw?timer control word register .............................................9-30 9.3.1.1 rdbk_cmd?read back command ............................9-31 9.3.1.2 ltch_cmd?counter latch command ........................9-31 9.3.2 sbyte_fmt?interval timer status byte format register ..........9-32 9.3.3 counter access ports register......................................................9-32 9.4 8259 interrupt controller (pic) registers ...................................................9-33 9.4.1 interrupt controller i/o map ..........................................................9-33 9.4.2 icw1?initialization command word 1 register ...........................9-34 9.4.3 icw2?initialization command word 2 register ...........................9-35 9.4.4 icw3?master controller initialization command word 3 register .........................................................................................9-35 82801BA ich2 and 82801BAm ich2-m datasheet xv 9.4.5 icw3?slave controller initialization command word 3 register..........................................................................................9-36 9.4.6 icw4?initialization command word 4 register ...........................9-36 9.4.7 ocw1?operational control word 1 (interrupt mask) register ....9-36 9.4.8 ocw2?operational control word 2 register ..............................9-37 9.4.9 ocw3?operational control word 3 register ..............................9-38 9.4.10 elcr1?master controller edge/level triggered register ..........9-39 9.4.11 elcr2?slave controller edge/level triggered register ............9-40 9.5 advanced interrupt controller (apic) .........................................................9-41 9.5.1 apic register map ........................................................................9-41 9.5.2 ind?index register ......................................................................9-41 9.5.3 dat?data register ......................................................................9-42 9.5.4 irqpa?irq pin assertion register .............................................9-42 9.5.5 eoir?eoi register ......................................................................9-43 9.5.6 id?identification register .............................................................9-43 9.5.7 ver?version register .................................................................9-44 9.5.8 arbid?arbitration id register .....................................................9-44 9.5.9 boot_config?boot configuration register .............................9-44 9.5.10 redirection table...........................................................................9-45 9.6 real time clock registers .........................................................................9-47 9.6.1 i/o register address map..............................................................9-47 9.6.2 indexed registers ..........................................................................9-47 9.6.2.1 rtc_rega?register a................................................9-48 9.6.2.2 rtc_regb?register b (general configuration) .........9-49 9.6.2.3 rtc_regc?register c (flag register) ......................9-50 9.6.2.4 rtc_regd?register d (flag register) ......................9-50 9.7 processor interface registers.....................................................................9-51 9.7.1 nmi_sc?nmi status and control register ..................................9-51 9.7.2 nmi_en?nmi enable (and real time clock index) ....................9-52 9.7.3 port92?fast a20 and init register............................................9-52 9.7.4 coproc_err?coprocessor error register ..............................9-52 9.7.5 rst_cnt?reset control register ..............................................9-53 9.8 power management registers (d31:f0) ....................................................9-54 9.8.1 power management pci configuration registers (d31:f0) ..........9-54 9.8.1.1 gen_pmcon_1?general pm configuration 1 register (pm?d31:f0) ..................................................9-54 9.8.1.2 gen_pmcon_2?general pm configuration 2 register (pm?d31:f0) ..................................................9-56 9.8.1.3 gen_pmcon_3?general pm configuration 3 register (pm?d31:f0) ..................................................9-57 9.8.1.4 gpi_rout?gpi routing control register (pm?d31:f0) ................................................................9-57 9.8.1.5 trp_fwd_en?io monitor trap forwarding enable register (pm?d31:f0)......................................9-58 9.8.1.6 mon[n]_trp_rng?i/o monitor [4:7] trap range register for devices 4?7 (pm?d31:f0) ........................9-59 9.8.1.7 mon_trp_msk?i/o monitor trap range mask register for devices 4?7 (pm?d31:f0) ........................9-59 9.8.2 apm i/o decode ............................................................................9-60 9.8.2.1 apm_cnt?advanced power management control port register ......................................................9-60 9.8.2.2 apm_sts?advanced power management status port register .......................................................9-60 xvi 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3 power management i/o registers.................................................9-61 9.8.3.1 pm1_sts?power management 1 status register.......9-62 9.8.3.2 pm1_en?power management 1 enable register........9-64 9.8.3.3 pm1_cnt?power management 1 control register .....9-65 9.8.3.4 pm1_tmr?power management 1 timer register .......9-66 9.8.3.5 proc_cnt?processor control register .....................9-66 9.8.3.6 lv2?level 2 register ...................................................9-67 9.8.3.7 lv3?level 3 register (82801BAm ich2-m) .................9-67 9.8.3.8 pm2_cnt?power management 2 control (82801BAm ich2-m)......................................................9-68 9.8.3.9 gpe0_sts?general purpose event 0 status register ..........................................................................9-68 9.8.3.10 gpe0_en?general purpose event 0 enables register ..........................................................................9-70 9.8.3.11 gpe1_sts?general purpose event 1 status register ..........................................................................9-71 9.8.3.12 gpe1_en?general purpose event 1 enable register ..........................................................................9-72 9.8.3.13 smi_en?smi control and enable register ..................9-72 9.8.3.14 smi_sts?smi status register ....................................9-74 9.8.3.15 mon_smi?device monitor smi status and enable register ..........................................................................9-75 9.8.3.16 devact_sts?device activity status register ...........9-76 9.8.3.17 devtrap_en?device trap enable register ..............9-77 9.8.3.18 bus_addr_track?bus address tracker register ..9-78 9.8.3.19 bus_cyc_track?bus cycle tracker register .........9-78 9.8.3.20 ss_cnt? speedstep? control register (82801BAm ich2-m)......................................................9-78 9.9 system management tco registers (d31:f0) ..........................................9-79 9.9.1 tco register i/o map ...................................................................9-79 9.9.2 tco1_rld?tco timer reload and current value register......9-79 9.9.3 tco1_tmr?tco timer initial value register ............................9-80 9.9.4 tco1_dat_in?tco data in register ........................................9-80 9.9.5 tco1_dat_out?tco data out register..................................9-80 9.9.6 tco1_sts?tco1 status register..............................................9-80 9.9.7 tco2_sts?tco2 status register..............................................9-82 9.9.8 tco1_cnt?tco1 control register............................................9-83 9.9.9 tco2_cnt?tco2 control register............................................9-83 9.9.10 tco_message1 and tco_message2 registers ....................9-84 9.9.11 tco_wdstatus?tco2 control register .................................9-84 9.9.12 sw_irq_gen?software irq generation register.....................9-84 9.10 general purpose i/o registers (d31:f0) ...................................................9-85 9.10.1 gpio register i/o address map....................................................9-87 9.10.2 gpio_use_sel?gpio use select register ..............................9-87 9.10.3 gp_io_sel?gpio input/output select register ........................9-88 9.10.4 gp_lvl?gpio level for input or output register.......................9-89 9.10.5 gpo_blink?gpo blink enable register....................................9-90 9.10.6 gpi_inv?gpio signal invert register.........................................9-91 82801BA ich2 and 82801BAm ich2-m datasheet xvii 10 ide controller registers (d31:f1) ...........................................................................10-1 10.1 pci configuration registers (ide?d31:f1)...............................................10-1 10.1.1 vid?vendor id register (ide?d31:f1) ......................................10-2 10.1.2 did?device id register (ide?d31:f1) ......................................10-2 10.1.3 cmd?command register (ide?d31:f1) ...................................10-2 10.1.4 sts?device status register (ide?d31:f1) ...............................10-3 10.1.5 rid?revision id register (hub-pci?d30:f0) ...........................10-3 10.1.6 pi?programming interface (ide?d31:f1)...................................10-3 10.1.7 scc?sub class code (ide?d31:f1) .........................................10-4 10.1.8 bcc?base class code (ide?d31:f1) .......................................10-4 10.1.9 mlt?master latency timer (ide?d31:f1).................................10-4 10.1.10 bm_base?bus master base address register (ide?d31:f1) ...............................................................................10-4 10.1.11 ide_svid?subsystem vendor id (ide?d31:f1) .......................10-5 10.1.12 ide_sid?subsystem id (ide?d31:f1) ......................................10-5 10.1.13 ide_tim?ide timing register (ide?d31:f1) ............................10-5 10.1.14 slv_idetim?slave (drive 1) ide timing register (ide?d31:f1) ...............................................................................10-7 10.1.15 sdma_cnt?synchronous dma control register (ide?d31:f1) ...............................................................................10-8 10.1.16 sdma_tim?synchronous dma timing register (ide?d31:f1) ...............................................................................10-8 10.1.17 ide_config?ide i/o configuration register.............................10-9 10.2 bus master ide i/o registers (d31:f1)....................................................10-11 10.2.1 bmic[p,s]?bus master ide command register .......................10-11 10.2.2 bmis[p,s]?bus master ide status register ..............................10-12 10.2.3 bmid[p,s]?bus master ide descriptor table pointer register .10-12 11 usb controller registers.........................................................................................11-1 11.1 pci configuration registers (d31:f2/f4) ...................................................11-1 11.1.1 vid?vendor identification register (usb?d31:f2/f4) ...............11-1 11.1.2 did?device identification register (usb?d31:f2/f4) ...............11-2 11.1.3 cmd?command register (usb?d31:f2/f4) .............................11-2 11.1.4 sta?device status register (usb?d31:f2/f4) ........................11-3 11.1.5 rid?revision identification register (usb?d31:f2/f4) ............11-3 11.1.6 pi?programming interface (usb?d31:f2/f4) ............................11-3 11.1.7 scc?sub class code register (usb?d31:f2/f4) ....................11-4 11.1.8 bcc?base class code register (usb?d31:f2/f4) ..................11-4 11.1.9 base?base address register (usb?d31:f2/f4)......................11-4 11.1.10 svid?subsystem vendor id (usb?d31:f2/f4).........................11-4 11.1.11 sid?subsystem id (usb?d31:f2/f4)........................................11-5 11.1.12 intr_ln?interrupt line register (usb?d31:f2/f4) .................11-5 11.1.13 intr_pn?interrupt pin register (usb?d31:f2/f4)...................11-5 11.1.14 sb_relnum?serial bus release number register (usb?d31:f2/f4).........................................................................11-5 11.1.15 usb_legkey?usb legacy keyboard/mouse control register (usb?d31:f2/f4) ..........................................................11-6 11.1.16 usb_res?usb resume enable register (usb?d31:f2/f4).........................................................................11-7 11.2 usb i/o registers.......................................................................................11-8 11.2.1 usbcmd?usb command register ............................................11-8 11.2.2 usbsta?usb status register ..................................................11-11 xviii 82801BA ich2 and 82801BAm ich2-m datasheet 11.2.3 usbintr?interrupt enable register..........................................11-12 11.2.4 frnum?frame number register..............................................11-12 11.2.5 frbaseadd?frame list base address ...................................11-13 11.2.6 sofmod?start of frame modify register.................................11-13 11.2.7 portsc[0,1]?port status and control register........................11-14 12 smbus controller registers (d31:f3) .....................................................................12-1 12.1 pci configuration registers (smbus?d31:f3)........................................12-1 12.1.1 vid?vendor identification register (smbus?d31:f3)...............12-1 12.1.2 did?device identification register (smbus?d31:f3) ...............12-1 12.1.3 cmd?command register (smbus?d31:f3).............................12-2 12.1.4 sta?device status register (smbus?d31:f3) ........................12-2 12.1.5 rid?revision id register (smbus?d31:f3).............................12-3 12.1.6 pi?programming interface (smbus?d31:f3)............................12-3 12.1.7 scc?sub class code register (smbus?d31:f3)....................12-3 12.1.8 bcc?base class code register (smbus?d31:f3) ..................12-3 12.1.9 smb_base?smbus base address register (smbus?d31:f3) ........................................................................12-4 12.1.10 svid?subsystem vendor id (smbus?d31:f2/f4) ...................12-4 12.1.11 sid?subsystem id (smbus?d31:f2/f4) ..................................12-4 12.1.12 intr_ln?interrupt line register (smbus?d31:f3) .................12-4 12.1.13 intr_pn?interrupt pin register (smbus?d31:f3) ..................12-5 12.1.14 hostc?host configuration register (smbus?d31:f3) ...........12-5 12.2 smbus i/o registers ..................................................................................12-6 12.2.1 hst_sts?host status register ..................................................12-7 12.2.2 hst_cnt?host control register ................................................12-8 12.2.3 hst_cmd?host command register...........................................12-9 12.2.4 xmit_slva?transmit slave address register ...........................12-9 12.2.5 hst_d0?data 0 register.............................................................12-9 12.2.6 hst_d1?data 1 register.............................................................12-9 12.2.7 block_db?block data byte register ......................................12-10 12.2.8 rcv_slva?receive slave address register ...........................12-10 12.2.9 slv_data?receive slave data register .................................12-10 12.2.10 smlink_pin_ctl?smlink pin control register.....................12-11 12.2.11 smbus_pin_ctl?smbus pin control register .......................12-11 13 ac?97 audio controller registers (d31:f5).............................................................13-1 13.1 ac?97 audio pci configuration space (d31:f5) ........................................13-1 13.1.1 vid?vendor identification register (audio?d31:f5) ..................13-1 13.1.2 did?device identification register (audio?d31:f5)...................13-2 13.1.3 pcicmd?pci command register (audio?d31:f5) ...................13-2 13.1.4 pcists?pci device status register (audio?d31:f5)...............13-3 13.1.5 rid?revision identification register (audio?d31:f5)................13-3 13.1.6 pi?programming interface register (audio?d31:f5) .................13-3 13.1.7 scc?sub class code register (audio?d31:f5) .......................13-4 13.1.8 bcc?base class code register (audio?d31:f5)......................13-4 13.1.9 hedt?header type register (audio?d31:f5) ..........................13-4 13.1.10 nambar?native audio mixer base address register (audio?d31:f5) ............................................................................13-5 13.1.11 nabmbar?native audio bus mastering base address register (audio?d31:f5)..............................................................13-5 13.1.12 svid?subsystem vendor id register (audio?d31:f5)..............13-6 82801BA ich2 and 82801BAm ich2-m datasheet xix 13.1.13 sid?subsystem id register (audio?d31:f5).............................13-6 13.1.14 intr_ln?interrupt line register (audio?d31:f5) .....................13-6 13.1.15 intr_pn?interrupt pin register (audio?d31:f5) ......................13-7 13.2 ac?97 audio i/o space (d31:f5)................................................................13-7 13.2.1 x_bdbar?buffer descriptor base address register ..................13-9 13.2.2 x_civ?current index value register .........................................13-10 13.2.3 x_lvi?last valid index register ................................................13-10 13.2.4 x_sr?status register ................................................................13-11 13.2.5 x_picb?position in current buffer register ..............................13-12 13.2.6 x_piv?prefetched index value register ....................................13-12 13.2.7 x_cr?control register ..............................................................13-13 13.2.8 glob_cnt?global control register.........................................13-14 13.2.9 glob_sta?global status register ..........................................13-15 13.2.10 cas?codec access semaphore register .................................13-16 14 ac?97 modem controller registers (d31:f6) ..........................................................14-1 14.1 ac?97 modem pci configuration space (d31:f6) .....................................14-1 14.1.1 vid?vendor identification register (modem?d31:f6) ...............14-1 14.1.2 did?device identification register (modem?d31:f6) ................14-2 14.1.3 pcicmd?pci command register (modem?d31:f6) ................14-2 14.1.4 pcista?device status register (modem?d31:f6) ...................14-3 14.1.5 rid?revision identification register (modem?d31:f6) .............14-3 14.1.6 pi?programming interface register (modem?d31:f6) ..............14-3 14.1.7 scc?sub class code register (modem?d31:f6).....................14-4 14.1.8 bcc?base class code register (modem?d31:f6) ...................14-4 14.1.9 hedt?header type register (modem?d31:f6)........................14-4 14.1.10 mmbar?modem mixer base address register (modem?d31:f6) .........................................................................14-4 14.1.11 mbar?modem base address register (modem?d31:f6) ........14-5 14.1.12 svid?subsystem vendor id (modem?d31:f6) .........................14-5 14.1.13 sid?subsystem id (modem?d31:f6) ........................................14-6 14.1.14 intr_ln?interrupt line register (modem?d31:f6) ..................14-6 14.1.15 int_pin?interrupt pin (modem?d31:f6) ...................................14-6 14.2 ac?97 modem i/o space (d31:f6) .............................................................14-7 14.2.1 x_bdbar?buffer descriptor list base address register ............14-8 14.2.2 x_civ?current index value register ...........................................14-9 14.2.3 x_lvi?last valid index register ..................................................14-9 14.2.4 x_sr?status register ................................................................14-10 14.2.5 x_picb?position in current buffer register ..............................14-11 14.2.6 x_piv?prefetch index value register ........................................14-11 14.2.7 x_cr?control register ..............................................................14-11 14.2.8 glob_cnt?global control register.........................................14-12 14.2.9 glob_sta?global status register ..........................................14-13 14.2.10 cas?codec access semaphore register .................................14-14 15 pinout and package information..............................................................................15-1 15.1 pinout..........................................................................................................15-1 15.2 package information .................................................................................15-14 xx 82801BA ich2 and 82801BAm ich2-m datasheet 16 electrical characteristics .........................................................................................16-1 16.1 absolute maximum ratings ........................................................................16-1 16.2 functional operating range.......................................................................16-1 16.3 d.c. characteristics....................................................................................16-2 16.4 a.c. characteristics ....................................................................................16-7 16.5 timing diagrams.......................................................................................16-18 17 testability.................................................................................................................1 7-1 17.1 test mode description................................................................................17-1 17.2 tri-state mode.............................................................................................17-2 17.3 xor chain mode........................................................................................17-2 17.3.1 xor chain testability algorithm example ....................................17-2 17.3.1.1 test pattern consideration for xor chain 4 .................17-3 a i/o register index..................................................................................................... a-1 b register bit index ..................................................................................................... b-1 82801BA ich2 and 82801BAm ich2-m datasheet xxi figures 2-1 required external rtc circuit....................................................................2-16 2-2 example v5ref sequencing circuit ..........................................................2-16 4-1 ich2 and system clock domains................................................................4-1 4-2 conceptual system clock diagram (82801BA ich2 and 82801BAm ich2-m)......................................................................................4-2 5-1 primary device status register error reporting logic.................................5-3 5-2 secondary status register error reporting logic ........................................5-3 5-3 nmi# generation logic .................................................................................5-4 5-4 integrated lan controller block diagram.....................................................5-7 5-5 64-word eeprom read instruction waveform .........................................5-17 5-6 lpc interface diagram ...............................................................................5-21 5-7 typical timing for lframe# ......................................................................5-24 5-8 abort mechanism ........................................................................................5-24 5-9 ich2 dma controller ..................................................................................5-26 5-10 dma serial channel passing protocol .......................................................5-30 5-11 dma request assertion through ldrq# ..................................................5-34 5-12 coprocessor error timing diagram ............................................................5-67 5-13 signal strapping..........................................................................................5-70 5-14 intel ? speedstep? block diagram (82801BAm ich2-m only) ..................5-85 5-15 physical region descriptor table entry ...................................................5-101 5-16 transfer descriptor ...................................................................................5-109 5-17 example queue conditions ......................................................................5-116 5-18 usb data encoding ..................................................................................5-119 5-19 usb legacy keyboard flow diagram ......................................................5-128 5-20 ich2 based ac?97 2.1..............................................................................5-143 5-21 ac?97 2.1 controller-codec connection...................................................5-144 5-22 ac-link protocol ........................................................................................5-145 5-23 ac-link powerdown timing.......................................................................5-151 5-24 sdin wake signaling ...............................................................................5-152 5-25 fwh memory cycle preamble .................................................................5-155 5-26 single byte read ......................................................................................5-155 5-27 single byte write ......................................................................................5-156 15-1 ich2 82801BA and ich2-m 82801BAm ballout (top view ? left side) ................................................................................15-2 15-2 ich2 82801BA and ich2-m 82801BAm ballout (top view ? right side)..............................................................................15-3 15-3 ich2 / ich2-m package (top and side views) ........................................15-14 15-4 ich2 / ich2-m package (bottom view)....................................................15-15 16-1 clock timing .............................................................................................16-18 16-2 valid delay from rising clock edge ........................................................16-18 16-3 setup and hold times ..............................................................................16-18 16-4 float delay................................................................................................16-18 16-5 pulse width...............................................................................................16-19 16-6 output enable delay.................................................................................16-19 16-7 ide pio mode...........................................................................................16-19 16-8 ide multiword dma...................................................................................16-20 16-9 ultra ata mode (drive initiating a burst read) ........................................16-20 16-10 ultra ata mode (sustained burst)............................................................16-21 16-11 ultra ata mode (pausing a dma burst)...................................................16-21 xxii 82801BA ich2 and 82801BAm ich2-m datasheet 16-12 ultra ata mode (terminating a dma burst) ............................................16-22 16-13 usb rise and fall times..........................................................................16-22 16-14 usb jitter..................................................................................................16-22 16-15 usb eop width........................................................................................16-23 16-16 smbus transaction ..................................................................................16-23 16-17 smbus time-out .......................................................................................16-23 16-18 power sequencing and reset signal timings (82801BA ich2 only)................................................................................16-24 16-19 power sequencing and reset signal timings (82801BAm ich2-m only).........................................................................16-24 16-20 1.8v/3.3v power sequencing...................................................................16-25 16-21 g3 (mechanical off) to s0 timings (82801BA ich2 only)........................16-25 16-22 g3 (mechanical off) to s0 timings (82801BAm ich2-m only) ................16-26 16-23 s0 to s1 to s0 timings (82801BA ich2 only) ..........................................16-26 16-24 s0 to s1 to s0 timings (82801BAm ich2-m only) ...................................16-27 16-25 s0 to s5 to s0 timings (82801BA ich2 only) ..........................................16-27 16-26 s0 to s5 to s0 timings (82801BAm ich2-m only) ...................................16-28 16-27 c0 to c2 to c0 timings ............................................................................16-28 16-28 c0 to c3 to c0 timings (82801BAm ich2-m only) ..................................16-29 17-1 test mode entry (xor chain example).....................................................17-1 17-2 example xor chain circuitry ....................................................................17-2 82801BA ich2 and 82801BAm ich2-m datasheet xxiii tables 1-1 industry specifications ..................................................................................1-1 1-2 pci devices and functions...........................................................................1-3 2-1 hub interface signals....................................................................................2-1 2-2 lan connect interface signals.....................................................................2-1 2-3 eeprom interface signals...........................................................................2-2 2-4 firmware hub interface signals....................................................................2-2 2-5 pci interface signals ....................................................................................2-2 2-6 ide interface signals ....................................................................................2-5 2-7 lpc interface signals ...................................................................................2-6 2-8 interrupt signals............................................................................................2-6 2-9 usb interface signals...................................................................................2-7 2-10 power management interface signals ..........................................................2-7 2-11 processor interface signals ..........................................................................2-9 2-12 sm bus interface signals............................................................................2-10 2-13 system management interface signals ......................................................2-10 2-14 real time clock interface...........................................................................2-11 2-15 other clocks ...............................................................................................2-11 2-16 miscellaneous signals ................................................................................2-11 2-17 ac?97 link signals......................................................................................2-12 2-18 general purpose i/o signals ......................................................................2-12 2-19 power and ground signals .........................................................................2-13 2-20 functional strap definitions ........................................................................2-14 2-21 test mode selection ...................................................................................2-15 3-1 ich2 power planes.......................................................................................3-1 3-2 integrated pull-up and pull-down resistors.................................................3-1 3-3 ide series termination resistors.................................................................3-2 3-4 power plane and states for output and i/o signals.....................................3-3 3-5 power plane for input signals.......................................................................3-6 5-1 type 0 configuration cycle device number translation ..............................5-5 5-2 i/o control hub 2 eeprom address map .................................................5-18 5-3 lpc cycle types supported.......................................................................5-21 5-4 start field bit definitions.............................................................................5-22 5-5 cycle type bit definitions ...........................................................................5-22 5-6 transfer size bit definition .........................................................................5-22 5-7 sync bit definition.....................................................................................5-23 5-8 ich2 response to sync failures................................................................5-23 5-9 dma transfer size......................................................................................5-28 5-10 address shifting in 16-bit i/o dma transfers .............................................5-28 5-11 dma cycle vs. i/o address ........................................................................5-32 5-12 pci data bus vs. dma i/o port size ..........................................................5-32 5-13 dma i/o cycle width vs. be[3:0]#..............................................................5-33 5-14 counter operating modes...........................................................................5-39 5-15 interrupt controller core connections ........................................................5-41 5-16 interrupt status registers ...........................................................................5-42 5-17 content of interrupt vector byte .................................................................5-42 5-18 apic interrupt mapping ..............................................................................5-49 5-19 arbitration cycles........................................................................................5-50 5-20 apic message formats..............................................................................5-51 5-21 eoi message ..............................................................................................5-51 xxiv 82801BA ich2 and 82801BAm ich2-m datasheet 5-22 short message............................................................................................5-52 5-23 apic bus status cycle definition ...............................................................5-53 5-24 lowest priority message (without focus processor) .................................5-54 5-25 remote read message ..............................................................................5-55 5-26 interrupt message address format ............................................................5-58 5-27 interrupt message data format..................................................................5-59 5-28 stop frame explanation .............................................................................5-61 5-29 data frame format ....................................................................................5-62 5-30 configuration bits reset by rtcrst# assertion ......................................5-65 5-31 init# going active......................................................................................5-67 5-32 nmi sources ...............................................................................................5-67 5-33 dp signal differences (82801BA ich2 only)..............................................5-68 5-34 frequency strap behavior based on exit state .........................................5-69 5-35 frequency strap bit mapping .....................................................................5-69 5-36 general power states for systems using ich2..........................................5-72 5-37 state transition rules for ich2 ..................................................................5-73 5-38 system power plane ..................................................................................5-74 5-39 causes of smi# and sci ............................................................................5-75 5-40 break events ..............................................................................................5-77 5-41 sleep types................................................................................................5-81 5-42 causes of wake events .............................................................................5-82 5-43 gpi wake events .......................................................................................5-82 5-44 sleep state exit latencies..........................................................................5-83 5-45 transitions due to power failure ..............................................................5-83 5-46 transitions due to power button ................................................................5-87 5-47 transitions due to ri# signal......................................................................5-88 5-48 write only registers with read paths in alternate access mode..............5-89 5-49 pic reserved bits return values...............................................................5-91 5-50 register write accesses in alternate access mode...................................5-91 5-51 ich2 clock inputs.......................................................................................5-93 5-52 alert on lan* message data......................................................................5-97 5-53 ide transaction timings (pci clocks) .....................................................5-100 5-54 interrupt/active bit interaction definition...................................................5-103 5-55 ultraata/33 control signal redefinitions.................................................5-105 5-56 frame list pointer bit description ............................................................5-108 5-57 td link pointer .........................................................................................5-109 5-58 td control and status ..............................................................................5-110 5-59 td token ..................................................................................................5-112 5-60 td buffer pointer ......................................................................................5-112 5-61 queue head block....................................................................................5-113 5-62 queue head link pointer .........................................................................5-113 5-63 queue element link pointer.....................................................................5-113 5-64 command register, status register and td status bit interaction .........5-115 5-65 queue advance criteria ...........................................................................5-117 5-66 usb schedule list traversal decision table ...........................................5-118 5-67 pid format ...............................................................................................5-120 5-68 pid types .................................................................................................5-121 5-69 address field............................................................................................5-121 5-70 endpoint field...........................................................................................5-122 5-71 token format ...........................................................................................5-123 5-72 sof packet ..............................................................................................5-123 82801BA ich2 and 82801BAm ich2-m datasheet xxv 5-73 data packet format ..................................................................................5-124 5-74 bits maintained in low power states..........................................................5-127 5-75 usb legacy keyboard state transitions..................................................5-129 5-76 quick protocol...........................................................................................5-131 5-77 send / receive byte protocol ...................................................................5-131 5-78 write byte/word protocol..........................................................................5-132 5-79 read byte/word protocol .........................................................................5-132 5-80 process call protocol................................................................................5-133 5-81 block read/write protocol ........................................................................5-135 5-82 i 2 c block read .........................................................................................5-136 5-83 slave write cycle format .........................................................................5-139 5-84 slave write registers ...............................................................................5-139 5-85 command types.......................................................................................5-140 5-86 read cycle format ...................................................................................5-140 5-87 data values for slave read registers .....................................................5-141 5-88 featured supported by ich2 ....................................................................5-142 5-89 ac?97 signals ...........................................................................................5-144 5-90 input slot 1 bit definitions.........................................................................5-149 5-91 output tag slot 0......................................................................................5-150 5-92 ac-link state during pcirst# ..................................................................5-153 6-1 pci devices and functions...........................................................................6-2 6-2 fixed i/o ranges decoded by ich2.............................................................6-3 6-3 variable i/o decode ranges ........................................................................6-5 6-4 memory decode ranges from processor perspective .................................6-6 7-1 pci configuration map (lan controller?b1:d8:f0)....................................7-1 7-2 configuration of subsystem id and subsystem vendor id via eeprom ......................................................................................................7-6 7-3 data register structure ..............................................................................7-10 7-4 ich2 integrated lan controller csr space ..............................................7-10 7-5 self-test results format ............................................................................7-15 7-6 statistical counters .....................................................................................7-20 8-1 pci configuration map (hub-pci?d30:f0) ................................................8-1 9-1 pci configuration map (lpc i/f?d31:f0)...................................................9-1 9-2 dma registers............................................................................................9-23 9-3 pic registers..............................................................................................9-33 9-4 apic direct registers .................................................................................9-41 9-5 apic indirect registers...............................................................................9-41 9-6 rtc i/o registers.......................................................................................9-47 9-7 rtc (standard) ram bank ........................................................................9-47 9-8 pci configuration map (pm?d31:f0) .......................................................9-54 9-9 apm register map......................................................................................9-60 9-10 acpi and legacy i/o register map............................................................9-61 9-11 tco i/o register map ................................................................................9-79 9-12 summary of gpio implementation .............................................................9-85 9-13 registers to control gpio ..........................................................................9-87 10-1 pci configuration map (ide?d31:f1).......................................................10-1 10-2 bus master ide i/o registers...................................................................10-11 11-1 pci configuration map (usb?d31:f2/f4) ................................................11-1 11-2 usb i/o registers.......................................................................................11-8 11-3 run/stop, debug bit interaction swdbg (bit 5), run/stop (bit 0) operation........................................................................11-10 12-1 pci configuration registers (smbus?d31:f3)........................................12-1 xxvi 82801BA ich2 and 82801BAm ich2-m datasheet 12-2 smb i/o registers ......................................................................................12-6 13-1 pci configuration map (audio?d31:f5) ...................................................13-1 13-2 ich2 audio mixer register configuration...................................................13-7 13-3 native audio bus master control registers ...............................................13-9 14-1 pci configuration map (modem?d31:f6).................................................14-1 14-2 ich2 modem mixer register configuration ................................................14-7 14-3 modem registers........................................................................................14-8 15-1 ich2 82801BA alphabetical ball list by signal name ...............................15-4 15-2 ich2-m 82801BAm alphabetical ball list by signal name ........................15-9 16-1 ich2-m power consumption measurements .............................................16-2 16-2 dc characteristic input signal association ................................................16-2 16-3 dc input characteristics.............................................................................16-3 16-4 dc characteristic output signal association .............................................16-4 16-5 dc output characteristics ..........................................................................16-5 16-6 other dc characteristics ............................................................................16-6 16-7 clock timings .............................................................................................16-7 16-8 pci interface timing ...................................................................................16-9 16-9 ide pio & multiword dma mode timing ..................................................16-10 16-10 ultra ata timing (mode 0, mode 1, mode 2) ...........................................16-11 16-11 ultra ata timing (mode 3, mode 4, mode 5) ...........................................16-11 16-12 universal serial bus timing......................................................................16-12 16-13 ioapic bus timing...................................................................................16-13 16-14 smbus timing ..........................................................................................16-13 16-15 ac?97 timing ............................................................................................16-13 16-16 lpc timing ...............................................................................................16-14 16-17 miscellaneous timings .............................................................................16-14 16-18 power sequencing and reset signal timings..........................................16-14 16-19 power management timings ....................................................................16-16 17-1 test mode selection ...................................................................................17-1 17-2 xor test pattern example ........................................................................17-2 17-3 xor chain #1 (rtcrst# asserted for 4 pci clocks while pwrok active) ..........................................................................................17-4 17-4 xor chain #2 (rtcrst# asserted for 5 pci clocks while pwrok active) ..........................................................................................17-5 17-5 xor chain #3 (rtcrst# asserted for 6 pci clocks while pwrok active) ..........................................................................................17-6 17-6 xor chain #4 (rtcrst# asserted for 7 pci clocks while pwrok active) ..........................................................................................17-7 17-7 signals not in xor chain ..........................................................................17-8 a-1 ich2 fixed i/o registers............................................................................. a-1 a-2 ich2 variable i/o registers ........................................................................ a-6 82801BA ich2 and 82801BAm ich2-m datasheet xxvii revision history revision description date -001 initial release. june 2000 -002 ? edits throughout for clarity ? added ich2-m: initial release october 2000 xxviii 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank 82801BA ich2 and 82801BAm ich2-m datasheet 1-1 introduction introduction 1 the intel ? 82801BA ich2 and intel ? 82801BAm ich2-m are a highly integrated multifunctional i/o controller hubs that provide the interface to the pci bus and integrate many of the functions needed in today?s pc platforms. the 82801BA is intended for desktop applications and the 82801BAm is intended for mobile applications. this datasheet provides a detailed description of the 82801BA and 82801BAm functions and capabilities including, signals, registers, on-chip functional units, interfaces, pinout, packaging, electrical characteristics, and testability. unless otherwise specified, all non-shaded areas describe the functionality of both components. in the non-shaded areas, the term "ich2" refers to both the 82801BA and 82801BAm components. 1.1 about this document this datasheet is intended for original equipment manufacturers and bios vendors creating ich2-based products. this document assumes a working knowledge of the vocabulary and principles of usb, ide, ac?97, smbus, pci, acpi, lan, and lpc. although some details of these features are described within this document, refer to the individual industry specifications listed in table 1-1 for the complete details. chapter 1. introduction chapter 1 introduces the ich2 and provides information on document organization. this chapter also describes the key features of the ich2 and provides a brief description of the major functions. chapter 2. signal description chapter 2 provides a detailed description of each ich2 signal. signals are arranged according to interface and details are provided as to the drive characteristics (input/output, open drain, etc.) of all signals. chapter 3. power planes and pin states chapter 3 provides a complete list of signals, their associated power well, their logic level in each suspend state, and their logic level before and after reset. chapter 4. system clock domains chapter 4 provides a list of each clock domain associated with the ich2 in an ich2-based system. s hading, as is shown here, indicates differences between the two components. in the shaded areas i ch2 refers to the 82801BA and ich2-m refers to the 82801BAm. table 1-1. industry specifications specification location lpc http://developer.intel.com/design/pcisets/lpc/ ac?97 http://developer.intel.com/pc-supp/platform/ac97/ wfm http://developer.intel.com/ial/wfm/usesite.htm smbus http://www.sbs-forum.org/specs.htm pci http://pcisig.com/specs.htm usb http://www.usb.org acpi http://www.teleport.com/~acpi/ introduction 1-2 82801BA ich2 and 82801BAm ich2-m datasheet chapter 5. functional description chapter 5 provides a detailed description of the functions in the ich2. all pci buses, devices and functions in this manual are abbreviated using the following nomenclature; bus:device:function. this datasheet abbreviates buses as b0 and b1, devices as d8, d30 and d31 and functions as f0, f1, f2, f3, f4, f5 and f6. for example device 31 function 5 is abbreviated as d31:f5, bus 1 device 8 function 0 is abbreviated as b1:d8:f0. generally, the bus number will not be used, and can be considered to be bus 0. note that the ich2?s external pci bus is typically bus 1; however, it may be assigned a different number depending on system configuration. chapter 6. register, memory and i/o address maps chapter 6 provides an overview of the registers, fixed i/o ranges, variable i/o ranges and memory ranges decoded by the ich2. chapter 7. lan controller registers chapter 7 provides a detailed description of all registers that reside in the ich2?s integrated lan controller. the integrated lan controller resides on the ich2?s external pci bus (typically bus 1) at device 8, function 0 (b1:d8:f0). chapter 8. hub interface to pci bridge registers chapter 8 provides a detailed description of all registers that reside in the hub interface to pci bridge. this bridge resides at device 30, function 0 (d30:f0). chapter 9. lpc bridge registers chapter 9 provides a detailed description of all registers that reside in the lpc bridge. this bridge resides at device 31, function 0 (d31:f0). this function contains registers for many different units within the ich2 including dma, timers, interrupts, cpu interface, gpio, power management, system management and rtc. chapter 10. ide controller registers chapter 10 provides a detailed description of all registers that reside in the ide controller. this controller resides at device 31, function 1 (d31:f1). chapter 11. usb controller registers chapter 11 provides a detailed description of all registers that reside in the two usb controllers. these controllers reside at device 31, functions 2 and 4 (d31:f2/f4). chapter 12. smbus controller registers chapter 12 provides a detailed description of all registers that reside in the smbus controller. this controller resides at device 31, function 3 (d31:f3). chapter 13. ac?97 audio controller registers chapter 13 provides a detailed description of all registers that reside in the audio controller. this controller resides at device 31, function 5 (d31:f5). note that this section of the datasheet does not include the native audio mixer registers. accesses to the mixer registers are forwarded over the ac-link to the codec where the registers reside. chapter 14. ac?97 modem controller registers chapter 14 provides a detailed description of all registers that reside in the modem controller. this controller resides at device 31, function 6 (d31:f6). note that this section of the datasheet does not include the modem mixer registers. accesses to the mixer registers are forwarded over the ac-link to the codec where the registers reside. chapter 15. pinout and package information chapter 15 provides the ball assignment for the 360 ebga package. the chapter also provides the physical dimensions and characteristics of the 360 ebga package. chapter 16. electrical characteristics chapter 16 provides the ac and dc characteristics including timing diagrams. chapter 17. testability chapter 17 provides details about the implementation of test modes on the ich2. index there are indexes listing registers and register bits. 82801BA ich2 and 82801BAm ich2-m datasheet 1-3 introduction 1.2 overview the ich2 provides extensive i/o support. functions and capabilities include: ? pci rev 2.2 compliant with support for 33 mhz pci operations. ? pci slots (supports up to 6 req/gnt pairs) ? acpi power management logic support ? enhanced dma controller, interrupt controller, and timer functions ? integrated ide controller supports ultra ata100/66/33) ? usb host interface with support for 4 usb ports; 2 host controllers ? integrated lan controller ? system management bus (smbus) with additional support for i 2 c devices ? ac?97 2.1 compliant link for audio and telephony codecs (up to 6 channels) ? low pin count (lpc) interface ? firmware hub (fwh) interface support ? alert on lan* (aol) and alert on lan 2 (aol2)* the ich2 incorporates a variety of pci functions that are divided into two logical devices (30 and 31) on pci bus 0 and one device on bus 1. device 30 is the hub interface-to-pci bridge. device 31 contains all the other pci functions, except the lan controller as shown in table 1-2 . the lan controller is located on bus 1. table 1-2. pci devices and functions bus:device:function function description bus 0:device 30:function 0 hub interface to pci bridge bus 0:device 31:function 0 pci to lpc bridge (includes: dma, timers, compatible interrupt controller, apic, rtc, processor interface control, power management control, system management control, and gpio control) bus 0:device 31:function 1 ide controller bus 0:device 31:function 2 usb controller #1 bus 0:device 31:function 3 smbus controller bus 0:device 31:function 4 usb controller #2 bus 0:device 31:function 5 ac?97 audio controller bus 0:device 31:function 6 ac?97 modem controller bus 1:device 8:function 0 lan controller introduction 1-4 82801BA ich2 and 82801BAm ich2-m datasheet the following sub-sections provide an overview of the ich2 capabilities. hub architecture as i/o speeds increase, the demand placed on the pci bus by the i/o bridge has become significant. with the addition of ac?97 and ultra ata/100, coupled with the existing usb, i/o requirements could impact pci bus performance. the chipset?s hub interface architecture ensures that the i/o subsystem; both pci and the integrated i/o features (ide, ac?97, usb, etc.), will receive adequate bandwidth. by placing the i/o bridge on the hub interface (instead of pci), the hub architecture ensures that both the i/o functions integrated into the ich2 and the pci peripherals obtain the bandwidth necessary for peak performance. pci interface the ich2 pci interface provides a 33 mhz, rev. 2.2 compliant implementation. all pci signals are 5v tolerant, except pme#. the ich2 integrates a pci arbiter that supports up to six external pci bus masters in addition to the internal ich2 requests. ide interface (bus master capability and synchronous dma mode) the fast ide interface supports up to four ide devices providing an interface for ide hard disks and cd roms. each ide device can have independent timings. the ide interface supports pio ide transfers up to 14 mbytes/sec and bus master ide transfers up 100 mbytes/sec. it does not consume any isa dma resources. the ide interface integrates 16x32-bit buffers for optimal transfers. the ich2?s ide system contains two independent ide signal channels. they can be electrically isolated independently. they can be configured to the standard primary and secondary channels (four devices). there are integrated series resistors on the data and control lines (see section 5.15, ?ide controller (d31:f1)? on page 5-99 for details). low pin count (lpc) interface the ich2 implements an lpc interface as described in the lpc 1.0 specification. the low pin count (lpc) bridge function of the ich2 resides in pci device 31:function 0. in addition to the lpc bridge interface function, d31:f0 contains other functional units including dma, interrupt controllers, timers, power management, system management, gpio, and rtc. note that in the current chipset platform, the super i/o (sio) component has migrated to the low pin count (lpc) interface. migration to the lpc interface allows for lower cost super i/o designs. 82801BA ich2 and 82801BAm ich2-m datasheet 1-5 introduction compatibility modules (dma controller, timer/counters, interrupt controller) the dma controller incorporates the logic of two 82c37 dma controllers, with seven independently programmable channels. channels 0?3 are hardwired to 8-bit, count-by-byte transfers, and channels 5?7 are hardwired to 16-bit, count-by-word transfers. any two of the seven dma channels can be programmed to support fast type-f transfers. the ich2 supports two types of dma (lpc and pc/pci). dma via lpc is similar to isa dma. lpc dma and pc/pci dma use the ich2?s dma controller. the pc/pci protocol allows pci-based peripherals to initiate dma cycles by encoding requests and grants via two pc/pci req#/gnt# pairs. lpc dma is handled through the use of the ldrq# lines from peripherals and special encodings on lad[3:0] from the host. single, demand, verify, and increment modes are supported on the lpc interface. channels 0?3 are 8 bit channels. channels 5?7 are 16 bit channels. channel 4 is reserved as a generic bus master request. the timer/counter block contains three counters that are equivalent in function to those found in one 82c54 programmable interval timer. these three counters are combined to provide the system timer function, and speaker tone. the 14.31818-mhz oscillator input provides the clock source for these three counters. the ich2 provides an isa-compatible interrupt controller that incorporates the functionality of two 82c59 interrupt controllers. the two interrupt controllers are cascaded so that 14 external and two internal interrupts are possible. in addition, the ich2 supports a serial interrupt scheme. all of the registers in these modules can be read and restored. this is required to save and restore system state after power has been removed and restored to the circuit. advanced programmable interrupt controller (apic) in addition to the standard isa compatible interrupt controller (pic) described in the previous section, the ich2 incorporates the advanced programmable interrupt controller (apic). while the standard interrupt controller is intended for use in a uni-processor system, apic can be used in either a uni-processor or multi-processor system. enhanced universal serial bus (usb) controller the usb controller provides enhanced support for the universal host controller interface (uhci). this includes support that allows legacy software to use a usb-based keyboard and mouse. the ich2 is usb revision 1.1 compliant. the ich2 contains two usb host controllers. each host controller includes a root hub with two separate usb ports each, for a total of 4 usb ports. see section 5.16, ?usb controller (device 31:functions 2 and 4)? on page 5-108 for details. introduction 1-6 82801BA ich2 and 82801BAm ich2-m datasheet lan controller the ich2?s integrated lan controller includes a 32-bit pci controller that provides enhanced scatter-gather bus mastering capabilities and enables the lan controller to perform high speed data transfers over the pci bus. its bus master capabilities enable the component to process high- level commands and perform multiple operations; this lowers processor utilization by off-loading communication tasks from the processor. two large transmit and receive fifos of 3 kb each help prevent data underruns and overruns while waiting for bus accesses. this enables the integrated lan controller to transmit data with minimum interframe spacing (ifs). the lan controller can operate in either full duplex or half duplex mode. in full duplex mode the lan controller adheres with the ieee 802.3x flow control specification. half duplex performance is enhanced by a proprietary collision reduction mechanism. see section 5.2, ?lan controller (b1:d8:f0)? on page 5-6 for details. rtc the ich2 contains a motorola* mc146818a-compatible real-time clock with 256 bytes of battery-backed ram. the real-time clock performs two key functions: keeping track of the time of day and storing system data, even when the system is powered down. the rtc operates on a 32.768 khz crystal and a separate 3v lithium battery that provides up to 7 years of protection. the rtc also supports two lockable memory ranges. by setting bits in the configuration space, two 8-byte ranges can be locked to read and write accesses. this prevents unauthorized reading of passwords or other system security information. the rtc also supports a date alarm that allows for scheduling a wake up event up to 30 days in advance, rather than just 24 hours in advance. gpio various general purpose inputs and outputs are provided for custom system design. the number of inputs and outputs varies depending on ich2 configuration. enhanced power management the ich2?s power management functions include enhanced clock control, local and global monitoring support for 14 individual devices, and various low-power (suspend) states (e.g., suspend-to-dram and suspend-to-disk). a hardware-based thermal management circuit permits software-independent entrance to low-power states. the ich2 contains full support for the advanced configuration and power interface (acpi) specification. for the ich2-m 82801BAm, the intel ? speedstep ? technology feature enables a mobile system to operate in multiple processor performance/thermal states and to transition smoothly between them. the internal processor clock setting and processor supply voltage setting determines these states. the ich2-m supports one low power mode and one high performance mode. the ich2-m?s pci clock can be dynamically controlled independent of any other low-power state (dynamic pci clock control). 82801BA ich2 and 82801BAm ich2-m datasheet 1-7 introduction system management bus (smbus) the ich2 contains an smbus host interface that allows the processor to communicate with smbus slaves. this interface is compatible with most i 2 c devices. special i 2 c commands are implemented (e.g., the i 2 c read that allows the ich2 to perform block reads of i 2 c devices). the ich2?s smbus host controller provides a mechanism for the processor to initiate communications with smbus peripherals (slaves). the host controller supports seven smbus interface command protocols for communicating with smbus slave devices (see system management bus specifications, rev 1.0): quick command, send byte, receive byte, write byte/word, read byte/word, process call, and block read/write. manageability the ich2 integrates several functions designed to manage the system and lower the total cost of ownership (tc0) of the system. these system management functions are designed to report errors, diagnose the system, and recover from system lockups without the aid of an external microcontroller. ? tco timer. the ich2?s integrated programmable tc0 timer is used to detect system locks. the first expiration of the timer generates an smi# that the system can use to recover from a software lock. the second expiration of the timer causes a system reset to recover from a hardware lock. ? processor present indicator. the ich2 looks for the processor to fetch the first instruction after reset. if the processor does not fetch the first instruction, the ich2 will reboot the system at the safe-mode frequency multiplier. ? ecc error reporting. when detecting an ecc error, the host controller has the ability to send one of several messages to the ich2. the host controller can instruct the ich2 to generate either an smi#, nmi, serr#, or tco interrupt. ? function disable. the ich2 provides the ability to disable the following functions: ac?97 modem, ac?97 audio, ide, usb, or smbus. once disabled, these functions no longer decode i/o, memory, or pci configuration space. also, no interrupts or power management events are generated from the disable functions. ? intruder detect. the ich2 provides an input signal (intruder#) that can be attached to a switch that is activated by the system case being opened. the ich2 can be programmed to generate an smi# or tco interrupt due to an active intruder# signal. ? smbus. the ich2 integrates an smbus controller that provides an interface to manage peripherals (e.g., serial presence detection (spd) or rimms and thermal sensors). ? alert-on-lan*. the ich2 supports alert-on-lan* and alert-on-lan* 2. in response to a tco event (intruder detect, thermal event, processor not booting) the ich2 sends a message over the smbus. a lan controller can decode this smbus message and send a message over the network to alert the network manager. introduction 1-8 82801BA ich2 and 82801BAm ich2-m datasheet ac?97 2.1 controller the audio codec ?97 (ac?97) specification defines a digital interface that can be used to attach an audio codec (ac), a modem codec (mc), an audio/modem codec (amc) or both an ac and an mc. the ac?97 specification defines the interface between the system logic and the audio or modem codec, known as the ac?97 digital link . the ich2?s ac?97 (with the appropriate codecs) not only replaces isa audio and modem functionality, but also improves overall platform integration by incorporating the ac?97 digital link. the use of the ich2-integrated ac?97 digital link reduces cost and eases migration from isa. by using an audio codec, the ac?97 digital link allows for cost-effective, high-quality, integrated audio on intel?s chipset-based platform. in addition, an ac?97 soft modem can be implemented with the use of a modem codec. several system options exist when implementing ac?97. the ich2-integrated digital link allows several external codecs to be connected to the ich2. the system designer can provide audio with an audio codec, a modem with a modem codec, or an integrated audio/modem codec. the digital link is expanded to support two audio codecs or a combination of an audio and modem codec. the modem implementations for different countries must be taken into consideration, because telephone systems may vary. by using a split design, the audio codec can be on-board and the modem codec can be placed on a riser. intel is developing an ac?97 digital link connector. with a single integrated codec, or amc, both audio and modem can be routed to a connector near the rear panel, where the external ports can be located. the digital link in the ich2 is compliant with revision 2.1 of the ac?97, so it supports two codecs with independent pci functions for audio and modem. microphone input and left and right audio channels are supported for a high quality, two-speaker audio solution. wake on ring from suspend also is supported with the appropriate modem codec. the ich2 expands the audio capability with support for up to six channels of pcm audio output (full ac3 decode). six-channel audio consists of front left, front right, back left, back right, center, and woofer, for a complete surround-sound effect. ich2 has expanded support for two audio codecs on the ac?97 digital link. 82801BA ich2 and 82801BAm ich2-m datasheet 2-1 signal description signal description 2 this chapter provides a detailed description of each signal. the signals are arranged in functional groups according to their associated interface. the ?#? symbol at the end of the signal name indicates that the active, or asserted state occurs when the signal is at a low voltage level. when ?#? is not present, the signal is asserted when at the high voltage level. the following notations are used to describe the signal type: i input pin o output pin od open drain output pin. i/o bi-directional input / output pin. 2.1 hub interface to host controller 2.2 link to lan connect table 2-1. hub interface signals name type description hl[11:0] i/o hub interface signals hl_stb i/o hub interface strobe: one of two differential strobe signals used to transmit and receive data through the hub interface. hl_stb# i/o hub interface strobe complement: second of the two differential strobe signals. hlcomp i/o hub interface compensation: used for hub interface buffer compensation. table 2-2. lan connect interface signals name type description lan_clk i lan interface clock: this signal is driven by the lan connect component. the frequency range is 0.8 mhz to 50 mhz. lan_rxd[2:0] i received data: the lan connect component uses these signals to transfer data and control information to the integrated lan controller. these signals have integrated weak pull-up resistors. lan_txd[2:0] o transmit data : the integrated lan controller uses these signals to transfer data and control information to the lan connect component. lan_rstsync o lan reset/sync: the lan connect component?s reset and sync signals are multiplexed onto this pin. signal description 2-2 82801BA ich2 and 82801BAm ich2-m datasheet 2.3 eeprom interface 2.4 firmware hub interface 2.5 pci interface table 2-3. eeprom interface signals name type description ee_shclk o eeprom shift clock: ee_shclk is the serial shift clock output to the eeprom. ee_din i eeprom data in: ee_din transfers data from the eeprom to the ich2. this signal has an integrated pull-up resistor. ee_dout o eeprom data out: ee_dout transfers data from the ich2 to the eeprom. ee_cs o eeprom chip select: ee_cs is a chip-select signal to the eeprom. table 2-4. firmware hub interface signals name type description fwh[3:0] / lad[3:0] i/o firmware hub signals: these signals are muxed with lpc address signals. fwh[4] / lframe# i/o firmware hub signals: this signal is muxed with lpc lframe# signal. table 2-5. pci interface signals name type description ad[31:0] i/o pci address/data: ad[31:0] is a multiplexed address and data bus. during the first clock of a transaction, ad[31:0] contain a physical address (32 bits). during subsequent clocks, ad[31:0] contain data. the ich2 drives all 0s on ad[31:0] during the address phase of all pci special cycles. c/be[3:0]# i/o bus command and byte enables: the command and byte enable signals are multiplexed on the same pci pins. during the address phase of a transaction, c/be[3:0]# define the bus command. during the data phase, c/be[3:0]# define the byte enables. c/be[3:0]# command type 0000 interrupt acknowledge 0001 special cycle 0010 i/o read 0011 i/o write 0110 memory read 0111 memory write 1010 configuration read 1011 configuration write 1100 memory read multiple 1110 memory read line 1111 memory write and invalidate all command encodings not shown are reserved. the ich2 does not decode reserved values, and therefore will not respond if a pci master generates a cycle using one of the reserved values. 82801BA ich2 and 82801BAm ich2-m datasheet 2-3 signal description devsel# i/o device select: the ich2 asserts devsel# to claim a pci transaction. as an output, the ich2 asserts devsel# when a pci master peripheral attempts an access to an internal ich2 address or an address destined for the hub interface (main memory or agp). as an input, devsel# indicates the response to an ich2- initiated transaction on the pci bus. devsel# is tri-stated from the leading edge of pcirst#. devsel# remains tri-stated by the ich2 until driven by a target device. frame# i/o cycle frame: the current initiator drives frame# to indicate the beginning and duration of a pci transaction. while the initiator asserts frame#, data transfers continue. when the initiator negates frame#, the transaction is in the final data phase. frame# is an input to the ich2 when the ich2 is the target, and frame# is an output from the ich2 when the ich2 is the initiator. frame# remains tri-stated by the ich2 until driven by an initiator. irdy# i/o initiator ready: irdy# indicates the ich2's ability, as an initiator, to complete the current data phase of the transaction. it is used in conjunction with trdy#. a data phase is completed on any clock both irdy# and trdy# are sampled asserted. during a write, irdy# indicates the ich2 has valid data present on ad[31:0]. during a read, it indicates the ich2 is prepared to latch data. irdy# is an input to the ich2 when the ich2 is the target and an output from the ich2 when the ich2 is an initiator. irdy# remains tri-stated by the ich2 until driven by an initiator. trdy# i/o target ready: trdy# indicates the ich2's ability as a target to complete the current data phase of the transaction. trdy# is used in conjunction with irdy#. a data phase is completed when both trdy# and irdy# are sampled asserted. during a read, trdy# indicates that the ich2, as a target, has placed valid data on ad[31:0]. during a write, trdy# indicates the ich2, as a target is prepared to latch data. trdy# is an input to the ich2 when the ich2 is the initiator and an output from the ich2 when the ich2 is a target. trdy# is tri-stated from the leading edge of pcirst#. trdy# remains tri-stated by the ich2 until driven by a target. stop# i/o stop: stop# indicates that the ich2, as a target, is requesting the initiator to stop the current transaction. stop# causes the ich2, as an initiatior, to stop the current transaction. stop# is an output when the ich2 is a target and an input when the ich2 is an initiator. stop# is tri-stated from the leading edge of pcirst#. stop# remains tri-stated until driven by the ich2. par i/o calculated/checked parity: par uses "even" parity calculated on 36 bits, ad[31:0] plus c/be[3:0]#. "even" parity means that the ich2 counts the number of 1s within the 36 bits plus par and the sum is always even. the ich2 always calculates par on 36 bits, regardless of the valid byte enables. the ich2 generates par for address and data phases and only guarantees par to be valid one pci clock after the corresponding address or data phase. the ich2 drives and tri-states par identically to the ad[31:0] lines except that the ich2 delays par by exactly one pci clock. par is an output during the address phase (delayed one clock) for all ich2 initiated transactions. par is an output during the data phase (delayed one clock) when the ich2 is the initiator of a pci write transaction, and when it is the target of a read transaction. ich2 checks parity when it is the target of a pci write transaction. if a parity error is detected, the ich2 sets the appropriate internal status bits, and has the option to generate an nmi# or smi#. perr# i/o parity error: an external pci device drives perr# when it receives data that has a parity error. the ich2 drives perr# when it detects a parity error. the ich can either generate an nmi# or smi# upon detecting a parity error (either detected internally or reported via the perr# signal). req[0:4]# req[5]# / req[b]# / gpio[1] i pci requests: the ich2 supports up to 6 masters on the pci bus. req[5]# is muxed with pc/pci req[b]# (must choose one or the other, but not both). if not used for pci or pc/pci, req[5]#/req[b]# can instead be used as gpio[1]. note: req[0]# is programmable to have improved arbitration latency for supporting pci-based 1394 controllers. table 2-5. pci interface signals (continued) name type description signal description 2-4 82801BA ich2 and 82801BAm ich2-m datasheet gnt[0:4]# gnt[5]# / gnt[b]# / gpio[17]# o pci grants: the ich2 supports up to 6 masters on the pci bus. gnt[5]# is muxed with pc/pci gnt[b]# (must choose one or the other, but not both). if not needed for pci or pc/pci, gnt[5]# can instead be used as a gpio. pull-up resistors are not required on these signals. if pullups are used, they should be tied to the vcc3_3 power rail. gnt[b]#/gnt[5]#/gpio[17] has an internal pull- up. pciclk i pci clock: this is a 33 mhz clock. pciclk provides timing for all transactions on the pci bus. . pcirst# o pci reset: ich2 asserts pcirst# to reset devices that reside on the pci bus. the ich2 asserts pcirst# during power-up and when s/w initiates a hard reset sequence through the rc (cf9h) register. the ich2 drives pcirst# inactive a minimum of 1 ms after pwrok is driven active. the ich2 drives pcirst# active a minimum of 1 ms when initiated through the rc register. plock# i/o pci lock: plock# indicates an exclusive bus operation and may require multiple transactions to complete. ich2 asserts plock# when it performs non-exclusive transactions on the pci bus. serr# i system error: serr# can be pulsed active by any pci device that detects a system error condition. upon sampling serr# active, the ich2 has the ability to generate an nmi, smi#, or interrupt. pme# i pci power management event: pci peripherals drive pme# to wake the system from low-power states s1?s5. pme# assertion can also be enabled to generate an sci from the s0 state. in some cases the ich2 may drive pme# active due to an internal wake event. the ich2 will not drive pme# high, but it will be pulled up to vccsus3_3 by an internal pull-up resistor. clkrun# (ich2-m only) i/o pci clock run: for the ich2-m, clkrun# is used to support pci clock run protocol. this signal connects to pci devices that need to request clock re-start or prevention of clock stopping. req[a]# / gpio[0] req[b]# / req[5]# / gpio[1] i pc/pci dma request [a:b]: this request serializes isa-like dma requests for the purpose of running isa-compatible dma cycles over the pci bus. this is used by devices such as pci-based super i/o or audio codecs that need to perform legacy 8237 dma but have no isa bus. when not used for pc/pci requests, these signals can be used as general purpose inputs. instead, req[b]# can be used as the 6th pci bus request. gnt[a]# / gpio[16] gnt[b]# / gnt[5]# / gpio[17] o pc/pci dma acknowledges [a:b]: this grant serializes an isa-like dack# for the purpose of running dma/isa master cycles over the pci bus. this is used by devices such as pci-based super/io or audio codecs which need to perform legacy 8237 dma but have no isa bus. when not used for pc/pci, these signals can be used as general purpose outputs. gntb# can also be used as the 6th pci bus master grant output. these signal have internal pull-up resistors. table 2-5. pci interface signals (continued) name type description note:for 82801BAm ich2-m, this clock does not stop based on the stp_pci# signal. the pci clock only stops based on slp_s1# or slp_s3#. 82801BA ich2: plock# is ignored when pci masters are granted the bus. 82801BAm ich2-m: devices on the pci bus (other than the ich2-m) are not permitted to assert the plock# signal. 82801BA ich2 and 82801BAm ich2-m datasheet 2-5 signal description 2.6 ide interface table 2-6. ide interface signals name type description pdcs1#, sdcs1# o primary and secondary ide device chip selects for 100 range: these signals are for the ata command register block. this output signal is connected to the corresponding signal on the primary or secondary ide connector. pdcs3#, sdcs3# o primary and secondary ide device chip select for 300 range: these signals are for the ata control register block. this output signal is connected to the corresponding signal on the primary or secondary ide connector. pda[2:0], sda[2:0] o primary and secondary ide device address: these output signals are connected to the corresponding signals on the primary or secondary ide connectors. they are used to indicate which byte in either the ata command block or control block is being addressed. pdd[15:0], sdd[15:0] i/o primary and secondary ide device data: these signals directly drive the corresponding signals on the primary or secondary ide connector. there is a weak internal pull-down resistor on pdd[7] and sdd[7]. pddreq, sddreq i primary and secondary ide device dma request: these input signals are directly driven from the drq signals on the primary or secondary ide connector. it is asserted by the ide device to request a data transfer, and used in conjunction with the pci bus master ide function. they are not associated with any at-compatible dma channel. there is a weak internal pull-down resistor on these signals. pddack#, sddack# o primary and secondary ide device dma acknowledge: these signals directly drive the dak# signals on the primary and secondary ide connectors. each signal is asserted by the ich2 to indicate to the ide dma slave devices that a given data transfer cycle (assertion of dior# or diow#) is a dma data transfer cycle. this signal is used in conjunction with the pci bus master ide function and are not associated with any at-compatible dma channel. pdior# sdior# o primary and secondary disk i/o read (pio and non-ultra dma): this is the command to the ide device that it may drive data on the pdd or sdd lines. data is latched by the ich2 on the deassertion edge of pdior# or sdior#. the ide device is selected either by the ata register file chip selects (pdcs1# or sdcs1#, pdcs3# or sdcs3#) and the pda or sda lines, or the ide dma acknowledge (pddak# or sddak#). primary and secondary disk write strobe (ultra dma writes to disk): this is the data write strobe for writes to disk. when writing to disk, ich2 drives valid data on rising and falling edges of pdwstb or sdwstb. primary and secondary disk dma ready (ultra dma reads from disk): this is the dma ready for reads from disk. when reading from disk, ich2 deasserts prdmardy# or srdmardy# to pause burst data transfers. pdiow# sdiow# o primary and secondary disk i/o write (pio and non-ultra dma): this is the command to the ide device that it may latch data from the pdd or sdd lines. data is latched by the ide device on the deassertion edge of pdiow# or sdiow#. the ide device is selected either by the ata register file chip selects (pdcs1# or sdcs1#, pdcs3# or sdcs3#) and the pda or sda lines, or the ide dma acknowledge (pddak# or sddak#). primary and secondary disk stop (ultra dma): ich2 asserts this signal to terminate a burst. piordy siordy i primary and secondary i/o channel ready (pio): this signal keeps the strobe active (pdior# or sdior# on reads, pdiow# or sdiow# on writes) longer than the minimum width. it adds wait states to pio transfers. primary and secondary disk read strobe (ultra dma reads from disk) : when reading from disk, ich2 latches data on rising and falling edges of this signal from the disk. primary and secondary disk dma ready (ultra dma writes to disk) : when writing to disk, this is deasserted by the disk to pause burst data transfers. signal description 2-6 82801BA ich2 and 82801BAm ich2-m datasheet 2.7 lpc interface 2.8 interrupt interface table 2-7. lpc interface signals name type description lad[3:0] / fwh[3:0] i/o lpc multiplexed command, address, data: internal pull-ups are provided. lframe# / fwh[4] o lpc frame: lframe# indicates the start of an lpc cycle, or an abort. ldrq[1:0]# i lpc serial dma/master request inputs: these signals are used to request dma or bus master access. typically, they are connected to external super i/o device. an internal pull-up resistor is provided on these signals. table 2-8. interrupt signals name type description serirq i/o serial interrupt request: this pin implements the serial interrupt protocol. pirq[d:a]# i/od pci interrupt requests: in non-apic mode the pirqx# signals can be routed to interrupts 3:7, 9:12, 14, or 15 as described in the interrupt steering section. each pirqx# line has a separate route control register. in apic mode, these signals are connected to the internal i/o apic in the following fashion: pirq[a]# is connected to irq16, pirq[b]# to irq17, pirq[c]# to irq18, and pirq[d]# to irq19. this frees the isa interrupts. pirq[h]#, pirq[g:f]# / gpio[4:3], pirq[e]# i/od pci interrupt requests: in non-apic mode the pirqx# signals can be routed to interrupts 3:7, 9:12, 14 or 15 as described in the interrupt steering section. each pirqx# line has a separate route control register. in apic mode, these signals are connected to the internal i/o apic in the following fashion: pirq[e]# is connected to irq20, pirq[f]# to irq21, pirq[g]# to irq22, and pirq[h]# to irq23. this frees the isa interrupts. if not needed for interrupts, pirq[g:f] can be used as gpio. irq[14:15] i interrupt request 14:15: these interrupt inputs are connected to the ide drives. irq14 is used by the drives connected to the primary controller and irq15 is used by the drives connected to the secondary controller. apicclk i apic clock: the apic clock runs at 33.333 mhz. apicd[1:0] i/od apic data: these bi-directional open drain signals are used to send and receive data over the apic bus. as inputs, the data is valid on the rising edge of apicclk. as outputs, new data is driven from the rising edge of the apicclk. 82801BA ich2 and 82801BAm ich2-m datasheet 2-7 signal description 2.9 usb interface 2.10 power management interface table 2-9. usb interface signals name type description usbp0p, usbp0n, usbp1p, usbp1n i/o universal serial bus port 1:0 differential: these differential pairs are used to transmit data/address/command signals for ports 0 and 1 (usb controller 1). usbp2p, usbp2n, usbp3p, usbp3n i/o universal serial bus port 3:2 differential: these differential pairs are used to transmit data/address/command signals for ports 2 and 3 (usb controller 2). oc[3:0]# i overcurrent indicators: these signals set corresponding bits in the usb controllers to indicate that an overcurrent condition has occurred. table 2-10. power management interface signals name type description thrm# i thermal alarm: thrm# is an active low signal generated by external hardware to start the hardware clock throttling mode. this signal can also generate an smi# or an sci. slp_s1# (ich2-m only) o s1 sleep control: clock synthesizer or power plane control. this signal connects to clock synthesizer?s pwrdwn# signal. an optional use is to shut off power to non-critical systems when in the s1 (powered on suspend), s3 (suspend to ram), s4 (suspend to disk), or s5 (soft off) states. slp_s3# o s3 sleep control: power plane control. this signal is used to shut off power to all non-critical systems when in s3 (suspend to ram), s4 (suspend to disk) or s5 (soft off) states. slp_s5# o s5 sleep control: power plane control. this signal is used to shut power off to all non-critical systems when in the s4 (suspend to disk) or s5 (soft off) states. pwrok i power ok: when asserted, pwrok is an indication to the ich2 that core power and pciclk have been stable for at least 1 ms. pwrok can be driven asynchronously. when pwrok is negated, the ich2 asserts pcirst#. rsm_pwrok (ich2 0nly) i resume well power ok: when asserted, this signal is an indication to the ich2 that the resume well power (vccsus3_3, vccsus1_8) has been stable for at least 10 ms. lan_pwrok (ich2-m only) i lan power ok: when asserted, this signal is an indication to the ich2-m that the lan controller power (vcclan3_3, vcclan1_8) has been stable for at least 10 ms. pwrbtn# i power button: the power button will cause smi# or sci to indicate a system request to go to a sleep state. if the system is already in a sleep state, this signal will cause a wake event. if pwrbtn# is pressed for more than 4 seconds, this will cause an unconditional transition (power button override) to the s5 state with only the pwrbtn# available as a wake event. override will occur even if the system is in the s1-s4 states. this signal has an internal pull-up resistor. ri# i ring indicate: from the modem interface. this signal can be enabled as a wake event; this is preserved across power failures. rsmrst# i resume well reset: rsmrst# is used for resetting the resume power plane logic. signal description 2-8 82801BA ich2 and 82801BAm ich2-m datasheet sus_stat# / lpcpd# o suspend status: this signal is asserted by the ich2 to indicate that the system will be entering a low power state soon. this can be monitored by devices with memory that need to switch from normal refresh to suspend refresh mode. it can also be used by other peripherals as an indication that they should isolate their outputs that may be going to powered-off planes. this signal is called lpcpd# on the lpc interface. c3_stat# / gpio[21] (ich2-m only) o c3_stat#: this ich2-m signal is typically configured as c3_stat#. it is used for indicating to an agp device that a c3 state transition is beginning or ending. if c3_stat# functionality is not required, this signal can be used as a gpo. susclk o suspend clock: this signal is an output of the rtc generator circuit and is used by other chips for the refresh clock. vrmpwrgd (ich2) vrmpwrgd/ vgate (ich2-m) i vrm power good (ich2 and ich2-m): vrmpwrgd should be connected to be the processor?s vrm power good. vgate / vrmpwrgd (ich2-m only) i vrm power good gate (ich2-m): vgate is used for intel ? speedstep tm technology support. it is an output from the processor?s voltage regulator to indicate that the voltage is stable. this signal can go inactive during a intel ? speedstep tm transition. in non-intel ? speedstep tm technology systems this signal should be connected to the processor vrm power good. agpbusy# (ich2-m only) i agp bus busy: this signal supports the c3 state. it provides an indication that the agp device is busy. when this signal is asserted, the bm_sts bit will be set. if this functionality is not needed, this signal may be configured as a gpi. stp_pci# (ich2-m only) o stop pci clock: this signal is an output to the external clock generator to turn off the pci clock. it is used to support pci clkrun# protocol. if this functionality is not needed, this signal can be configured as a gpo. stp_cpu# (ich2-m only) o stop cpu clock: output to the external clock generator to turn off the processor clock. it is used to support the c3 state. if this functionality is not needed, this signal can be configured as a gpo. batlow# (ich2-m only) i battery low: input from battery to indicate that there is insufficient power to boot the system. assertion prevents wake from s1?s5 state. this signal can also be enabled to cause an smi# when asserted. in desktop configurations this signal should be pulled high to vccsus. cpuperf# (ich2-m only) od cpu performance: this signal is used for intel ? speedstep tm technology support. it selects which power state to put the processo in. if this functionality is not needed, this signal can be configured as a gpo. this is an open-drain output signal and requires an external pull-up to the processor i/o voltage. ssmuxsel (ich2-m only) o speedstep mux select: this signal is used for intel ? speedstep tm technology support. it selects the voltage level for the processor. if this functionality is not needed, this signal can be configured as a gpo. table 2-10. power management interface signals name type description 82801BA ich2 and 82801BAm ich2-m datasheet 2-9 signal description 2.11 processor interface table 2-11. processor interface signals name type description a20m# o mask a20: a20m# goes active based on setting the appropriate bit in the port 92h register, or based on the a20gate signal. speed strap: during the reset sequence, ich2 drives a20m# high if the corresponding bit is set in the freq_strp register. cpuslp# o processor sleep: this signal puts the processor into a state that saves substantial power compared to stop-grant state. however, during that time, no snoops occur. the ich2 can optionally assert the cpuslp# signal when going to the s1 state. ferr# i numeric coprocessor error: this signal is tied to the coprocessor error signal on the processor. ferr# is only used if the ich2 coprocessor error reporting function is enabled in the general control register (device 31:function 0, offset d0, bit 13). if ferr# is asserted, the ich2 generates an internal irq13 to its interrupt controller unit. it is also used to gate the ignne# signal to ensure that ignne# is not asserted to the processor unless ferr# is active. ferr# requires an external weak pull-up to ensure a high level when the coprocessor error function is disabled. ignne# o ignore numeric error: this signal is connected to the ignore error pin on the processor. ignne# is only used if the ich2 coprocessor error reporting function is enabled in the general control register (device 31:function 0, offset d0, bit 13). if ferr# is active, indicating a coprocessor error, a write to the coprocessor error register (f0h) causes the ignne# to be asserted. ignne# remains asserted until ferr# is negated. if ferr# is not asserted when the coprocessor error register is written, the ignne# signal is not asserted. speed strap: during the reset sequence, ich2 drives ignne# high if the corresponding bit is set in the freq_strp register. init# o initialization: init# is asserted by the ich2 for 16 pci clocks to reset the processor. ich2 can be configured to support processor bist. in that case, init# will be active when pcirst# is active. intr o processor interrupt: intr is asserted by the ich2 to signal the processor that an interrupt request is pending and needs to be serviced. it is an asynchronous output and normally driven low. speed strap: during the reset sequence, ich2 drives intr high if the corresponding bit is set in the freq_strp register. nmi o non-maskable interrupt: nmi is used to force a non-maskable interrupt to the processor. the ich2 can generate an nmi when either serr# or iochk# is asserted. the processor detects an nmi when it detects a rising edge on nmi. nmi is reset by setting the corresponding nmi source enable/disable bit in the nmi status and control register. speed strap: during the reset sequence, ich2 drives nmi high if the corresponding bit is set in the freq_strp register. smi# o system management interrupt: smi# is an active low output synchronous to pciclk. it is asserted by the ich2 in response to one of many enabled hardware or software events. stpclk# o stop clock request: stpclk# is an active low output synchronous to pciclk. it is asserted by the ich2 in response to one of many hardware or software events. when the processor samples stpclk# asserted, it responds by stopping its internal clock. signal description 2-10 82801BA ich2 and 82801BAm ich2-m datasheet 2.12 smbus interface 2.13 system management interface rcin# i keyboard controller reset processor: the keyboard controller can generate init# to the processor. this saves the external or gate with the ich2?s other sources of init#. when the ich2 detects the assertion of this signal, init# is generated for 16 pci clocks. . a20gate i a20 gate: this signal is from the keyboard controller. it acts as an alternative method to force the a20m# signal active. a20gate saves the external or gate needed with various other pcisets. cpupwrgd od processor power good (82801BA ich2): this signal should be connected to the processor?s pwrgood input. this is an open-drain output signal (external pull-up resistor required) that represents a logical and of the ich2?s pwrok and vrmpwrgd signals. cpu power good (82801BAm ich2-m): this signal should be connected to the processor?s pwrgood input. for intel ? speedstep? technology support, this signal is kept high during a intel ? speedstep? technology state transition to prevent loss of processor context. this is an open-drain output signal (external pull-up resistor required) that represents a logical and of the ich2-m?s pwrok and vgate / vrmpwrgd signals. table 2-12. sm bus interface signals name type description smbdata i/od smbus data: external pull-up is required. smbclk i/od smbus clock: external pull-up is required. smbalert# / gpio[11] i smbus alert: this signal is used to wake the system or generate an smi#. if not used for smbalert#, it can be used as a gpi. table 2-13. system management interface signals name type description intruder# i intruder detect: this signal can be set to disable system if box detected open. this signal?s status is readable, so it can be used like a gpi if the intruder detection is not needed. smlink[1:0] i/od system management link: these signals are an smbus link to an optional external system management asic or lan controller. external pull-ups are required. note that smlink[0] corresponds to an smbus clock signal and smlink[1] corresponds to an smbus data signal. table 2-11. processor interface signals (continued) name type description note 82801BA ich2: the 82801BA ignores rcin# assertion during transitions to the s3, s4 and s5 states. 82801BAm ich2-m: the 82801BAm ignores rcin# assertion during transitions to the s1, s3, s4 and s5 states. 82801BA ich2 and 82801BAm ich2-m datasheet 2-11 signal description 2.14 real time clock interface 2.15 other clocks 2.16 miscellaneous signals table 2-14. real time clock interface name type description rtcx1 special crystal input 1: this signal is connected to the 32.768 khz crystal. if no external crystal is used, then rtcx1 can be driven with the desired clock rate. rtcx2 special crystal input 2: this signal is connected to the 32.768 khz crystal. if no external crystal is used, then rtcx2 should be left floating. table 2-15. other clocks name type description clk14 i oscillator clock: clk14 is used for 8254 timers and runs at 14.31818 mhz. 82801BA ich2: this clock is permitted to stop during s3 (or lower) states. 82801BAm ich2-m: this clock is permitted to stop during s1 (or lower) states. clk48 i 48 mhz clock: clk48 is used to for the usb controller and runs at 48 mhz. 82801BA ich2: this clock is permitted to stop during s3 (or lower) states. 82801BAm ich2-m: this clock is permitted to stop during s1 (or lower) states. clk66 i 66 mhz clock: clk66 is used to for the hub interface and runs at 66 mhz. 82801BA ich2: this clock is permitted to stop during s3 (or lower) states. 82801BAm ich2-m: this clock is permitted to stop during s1 (or lower) states. table 2-16. miscellaneous signals name type description spkr o speaker: the spkr signal is the output of counter 2 and is internally "anded" with port 61h bit 1 to provide speaker data enable. this signal drives an external speaker driver device, which in turn drives the system speaker. upon pcirst#, its output state is 1. note: spkr is sampled at the rising edge of pwrok as a functional strap. see section 2.20.1 for more details. rtcrst# i rtc reset: when asserted, this signal resets register bits in the rtc well and sets the rtc_pwr_sts bit (bit 2 in gen_pmcon3 register). this signal is also used to enter the test modes documented in section 2.20.2 . note: clearing cmos in an ich2-based platform can be done by using a jumper on rtcrst# or gpi, or using safemode strap. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. tp0 (ich2 0nly) i test point (82801BA ich2): this signal must have an external pull-up to vccsus3_3. fs0 i functional strap: this signal is reserved for future use. there is an internal pull- up resistor on this signal. signal description 2-12 82801BA ich2 and 82801BAm ich2-m datasheet 2.17 ac?97 link note: if the aclink shutoff bit in the ac?97 global control register (see section 13.2.8 ) is set to 1, internal pull-down resistors will be enabled on ac_bit_clk and ac_sdata_in[1:0]. if aclink shutoff is cleared to 0, these pull-down resistors are disabled. if there is no codec down on the system board, the two signals ac_sdin[1:0] should be pulled down externally with a resistor to ground. 2.18 general purpose i/o table 2-17. ac?97 link signals name type description ac_rst# o ac97 reset: master h/w reset to external codec(s) ac_sync o ac97 sync: 48 khz fixed rate sample sync to the codec(s) ac_bit_clk i ac97 bit clock: 12.288 mhz serial data clock generated by the external codec(s). see note. ac_sdout o ac97 serial data out: serial tdm data output to the codec(s) note: ac_sdout is sampled at the rising edge of pwrok as a functional strap. see section 2.20.1 for more details. ac_sdin[1:0] i ac97 serial data in 0: serial tdm data inputs from the codecs. see note. table 2-18. general purpose i/o signals name type description gpio[31:29] o not implemented. gpio[28:27] i/o can be input or output. resume power well. unmuxed. gpio[26] i/o not implemented. gpio[25] i/o can be input or output. resume power well. not muxed. gpio[24] (ich2 only) i/o can be input or output. resume power well. gpio[23] (ich2 only) o fixed as output only. main power well. gpio[22] (ich2 only) od fixed as output only. main power well. open-drain output. gpio[21] o fixed as output only. main power well. gpio[20:18] (ich2 only) o fixed as output only. main power well. gpio[17:16] o fixed as output only. main power well. can instead be used for pc/pci gnt[a:b]#. gpio[17] can also alternatively be used for pci gnt[5]#. integrated pull-up resistor. gpio[15:14] i not implemented. gpio[13:12] i fixed as input only. resume power well. not muxed. gpio[11] i fixed as input only. resume power well. can instead be used for smbalert#. gpio[10:9] i not implemented. gpio[8] i fixed as input only. resume power well. not muxed. gpio[7] i fixed as input only. main power well. not muxed. gpio[6] (ich2 only) i fixed as input only. main power well. 82801BA ich2 and 82801BAm ich2-m datasheet 2-13 signal description 2.19 power and ground gpio[5] not implemented. gpio[4:3] i fixed as input only. main power well. can be used instead as pirq[g:f]#. gpio[2] not implemented. gpio[1:0] i fixed as input only. main power well. can instead be used for pc/pci req[a:b]#. gpio[1] can also alternatively be used for pci req[5]#. table 2-19. power and ground signals name description vcc3_3 3.3v supply for core well i/o buffers. this power may be shut off in s3, s5 or g3 states. vcc1_8 1.8v supply for core well logic. this power may be shut off in s3, s5 or g3 states. v5ref reference for 5v tolerance on core well inputs. this power may be shut off in s3, s5 or g3 states. hubref 0.9v reference for the hub interface. this power may be shut off in s3, s5 or g3 states. vccsus3_3 3.3v supply for resume well i/o buffers. this power is not expected to be shut off unless power is removed. ? 82801BA ich2: the system is unplugged. ? 82801BAm ich2-m: the main battery is removed or completely drained and ac power is not available. vccsus1_8 1.8v supply for resume well logic. this power is not expected to be shut off unless power is removed. ? 82801BA ich2: the system is unplugged. ? 82801BAm ich2-m: the main battery is removed or completely drained and ac power is not available. v5ref_sus reference for 5v tolerance on resume well inputs. this power is not expected to be shut off unless power is removed. ? 82801BA ich2: the system is unplugged. note that v5ref_sus only affects 5v tolerance for the usb oc[3:0]# pins and can be connected to vccsus3_3 if 5v tolerance on these signals is not required. ? 82801BAm ich2-m: the main battery is removed or completely drained and ac power is not available. vccrtc 3.3v (can drop to 2.0v min. in g3 state) supply for the rtc well. this power is not expected to be shut off unless the rtc battery is removed or completely drained. note: implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. clearing cmos in an ich2-based platform can be done by using a jumper on rtcrst# or gpi, or using safemode strap. vcclan3_3 (ich2-m only) 3.3v supply for lan connect interface buffers. this is a separate power plane that may or may not be energized in s3?s5 states depending upon the presence or absence of ac power and network connectivity. this plane must be on in s0 and s1. vcclan1_8 (ich2-m only) 1.8v supply for lan controller logic. this is a separate power plane that may or may not be energized in s3?s5 states depending upon the presence or absence of ac power and network connectivity. this plane must be on in s0 and s1. vbias rtc well bias voltage. the dc reference voltage applied to this pin sets a current that is mirrored throughout the oscillator and buffer circuitry. see section 2.20.3 . v_cpu_io powered by the same supply as the processor i/o voltage. this supply is used to drive the processor interface outputs. vss grounds. table 2-18. general purpose i/o signals (continued) name type description signal description 2-14 82801BA ich2 and 82801BAm ich2-m datasheet 2.20 pin straps 2.20.1 functional straps the following signals are used for static configuration. they are sampled at the rising edge of pwrok to select configurations and then revert later to their normal usage. to invoke the associated mode, the signal should be driven at least 4 pci clocks prior to the time it is sampled. table 2-20. functional strap definitions signal usage when sampled comment ac_sdout safe mode rising edge of pwrok the signal has a weak internal pull-down. if the signal is sampled high, the ich2 sets the processor speed strap pins for safe mode. refer to processor specification for speed strapping definition. the status of this strap is readable via the safe_mode bit (bit 2, d31: f0, offset d4h). ee_dout reserved system designers should include a placeholder for a pull-down resistor on ee_dout but do not populate the resistor . fs[0] reserved system designers should include a placeholder for a pull-down resistor on fs[0] but do not populate the resistor . gnt[a]# to p-sw a p override rising edge of pwrok the signal has a weak internal pull-up. if the signal is sampled low, the system is strapped to the ?top-swap? mode (ich2 will invert a16 for all cycles targeting fwh bios space). the status of this strap is readable via the top-swap bit (bit 13, d31: f0, offset d4h). note that software will not be able to clear the top-swap bit until the system is rebooted without gnt[a]# being pulled down. hlcomp enhanced hub interface mode during pcirst# assertion if this signal is sampled high (via an external pull-up to vcc1_8), the normal hub interface buffer mode will be selected. if this signal is sampled low (via an external pull-down), the enhanced hub interface buffer mode will be selected. see the specific platform design guide for resistor values and routing guidelines for each hub interface mode. spkr no reboot rising edge of pwrok the signal has a weak internal pull-up. if the signal is sampled low, the system is strapped to the ?no reboot? mode (ich2 will disable the tco timer system reboot feature). the status of this strap is readable via the no_reboot bit (bit 1, d31: f0, offset d4h). 82801BA ich2 and 82801BAm ich2-m datasheet 2-15 signal description 2.20.2 test signals 2.20.2.1 test mode selection when pwrok is active (high), driving rtcrst# low for a number of pci clocks (33 mhz) will activate a particular test mode as specified in table 2-21 . note: rtcrst# may be driven low any time after pcirst is inactive. refer to chapter 17, ?testability? for a detailed description of the ich2 test modes. 2.20.2.2 test straps (82801BA ich2 only) table 2-21. test mode selection number of pci clocks rtcrst# driven low after pwrok active test mode <4 no test mode selected 4 xor chain 1 5 xor chain 2 6 xor chain 3 7 xor chain 4 8 all ?z? 9?24 reserved. do not attempt >24 no test mode selected the ich2?s tp[0] (test point) signal must be pulled to vccsus3_3 with an external pull-up resistor. signal description 2-16 82801BA ich2 and 82801BAm ich2-m datasheet 2.20.3 external rtc circuitry to reduce rtc well power consumption, the ich2 implements an internal oscillator circuit that is sensitive to step voltage changes in vccrtc and vbias. figure 2-1 shows a schematic diagram of the circuitry required to condition these voltages to ensure correct operation of the ich2 rtc. 2.20.4 v5ref / vcc3_3 sequencing requirements v5ref and v5ref_sus are the reference voltages for 5v tolerance on inputs to the ich2. v5ref and v5ref_sus must power up before or simultaneous to vcc3_3 and vccsus3_3 respectively, and must power down after or simultaneous to vcc3_3 and vccsus3_3 respectively. refer to figure 2-2 for an example circuit schematic that may be used to ensure proper v5ref sequencing. note that separate circuits must be implemented for both the core and suspend well supplies. figure 2-1. required external rtc circuit c3 12.5 pf 3.3v vccsus 1 k ? vbatt 1 k ? c1 0.047 uf 32768 hz xtal r1 10 m ? r2 10 m ? c2 12.5 pf 1 f vccrtc rtcx2 rtcx1 vbias vssrtc note: capacitor c2 and c3 values are crystal-dependent. figure 2-2. example v5ref sequencing circuit vcc supply (3.3v) 5v supply 1k 1 uf 5vref to system to system schottky diode 82801BA ich2 and 82801BAm ich2-m datasheet 3-1 power planes and pin states power planes and pin states 3 3.1 power planes 3.2 integrated pull-ups and pull-downs table 3-1. ich2 power planes plane description main i/o (3.3v) vcc3_3: powered by the main power supply (or battery for the ich2-m). when the system is in the s3, s4, s5, or g3 state, this plane is assumed to be shut off. main logic (1.8v) vcc1_8: powered by the main power supply (or battery for the ich2-m). when the system is in the s3, s4, s5, or g3 state, this plane is assumed to be shut off. resume i/o (3.3v standby) vccsus3_3: powered by the main power supply (or battery for the ich2-m) in s0?s1 states. powered by the trickle power supply (or battery for the ich2-m) when the system is in the s3, s4, s5, state. assumed to be shut off only when in the g3 state (system is unplugged for the ich2 or battery removed for the ich2-m). resume logic (1.8v standby) vccsus1_8: powered by the main power supply (or battery for the ich2-m) in s0?s1 states. powered by the trickle power supply (or battery for the ich2-m) when the system is in the s3, s4, s5, state. assumed to be shut off only when in the g3 state (system is unplugged for the ich2 or batter removed for the ich2-m). processor interface (1.3 ~ 2.5v) v_cpu_io: powered by the main power supply via processor voltage regulator. when the system is in the s3, s4, s5, or g3 state, this plane is assumed to be shut off. lan i/o (3.3v) (ich2-m only) vcclan3_3: this is a separate power plane that may or may not be energized in s3 - s5 states depending upon the presence or absence of ac power and network connectivity. this plane must be on in the s0 and s1 states. lan logic (1.8v) (ich2-m only) vcclan1_8: this is a separate power plane that may or may not be energized in s3 - s5 states depending upon the presence or absence of ac power and network connectivity. this plane must be on in the s0 and s1 states. rtc vccrtc: when other power is available (from the main supply for the ich2 or battery for the ich2-m), external diode coupling will provide power to reduce the drain on the rtc battery. assumed to operate from 3.3v down to 2.0v. table 3-2. integrated pull-up and pull-down resistors signal resistor type nominal value notes ee_din pull-up 24 k ? 1 ee_dout pull-up 24 k ? 1 gnt[b:a]# / gnt[5]# / gpio[17:16] pull-up 24 k ? 1 lad[3:0]# / fwh[3:0]# pull-up 24 k ? 1 ldrq[1:0] pull-up 24 k ? 1 pme# pull-up 24 k ? 1 pwrbtn# pull-up 24 k ? 1 spkr pull-up 24 k ? 1, 5 ac_bitclk pull-down 20 k ? 2, 6 power planes and pin states 3-2 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. simulation data shows that these resistor values can range from 18 k ? to 42 k ? . 2. simulation data shows that these resistor values can range from 13 k ? to 38 k ? . 3. simulation data shows that these resistor values can range from 6 k ? to 14 k ? . 4. simulation data shows that these resistor values can range from 4.3 k ? to 20 k ? . 5. the pull-up or pull-down on this signal is only enabled at boot/reset for strapping function. 6. this pull-down is only enabled when the aclink shut off bit in the ac?97 global control register is set to 1. 3.3 ide integrated series termination resistors table 3-3 shows the ich2 ide signals that have integrated series termination resistors. note: simulation data indicates that the integrated series termination resistors are a nominal 33 ? but can range from 31 ? to 43 ? . 3.4 output and i/o signals planes and states table 3-4 shows the power plane associated with the output and i/o signals, as well as the state at various times. within the table, the following terms are used: ?high-z? tri-state. ich2 not driving the signal high or low. ?high? ich2 is driving the signal to a logic ?1? ?low? ich2 is driving the signal to a logic ?0? ?defined? driven to a level that is defined by the function (will be high or low) ?undefined? ich2 is driving the signal, but the value is indeterminate. ?running? clock is toggling or signal is transitioning because function not stopping ?off? the power plane is off, so ich2 is not driving note that the signal levels are the same in s4 and s5. ac_sdin[0] pull-down 20 k ? 2, 6 ac_sdin[1] pull-down 20 k ? 2, 6 ac_sdout pull-down 20 k ? 2, 6 ac_sync pull-down 20 k ? 2, 6 lan_rxd[2:0] pull-up 9 k ? 3 pdd[7] / sdd[7] pull-down 5.9 k ? 4 pddreq / sddreq pull-down 5.9 k ? 4 table 3-2. integrated pull-up and pull-down resistors (continued) signal resistor type nominal value notes table 3-3. ide series termination resistors signal integrated series termination resistor value pdd[15:0], sdd[15:0], pdiow#, sdiow#, pdior#, pdiow#, pdreq, sdreq, pddack#, sddack#, piordy, siordy, pda[2:0], sda[2:0], pdcs1#, sdcs1#, pdcs3#, sdcs3#, irq14, irq15 approximately 33 ? (see note) 82801BA ich2 and 82801BAm ich2-m datasheet 3-3 power planes and pin states table 3-4. power plane and states for output and i/o signals signal name power plane reset signal during reset immediately after reset c3 (ich2-m) s1 s3 s4/s5 pci bus ad[31:0] main i/o pcirst# high-z undefined defined defined off off c/be#[3:0] main i/o pcirst# high-z undefined defined defined off off clkrun# (ich2-m) main i/o pcirst# low low defined off off devsel# main i/o pcirst# high-z high-z high-z high-z off off frame# main i/o pcirst# high-z high-z high-z high-z off off gnt[0:5]# main i/o pcirst# high high high high off off gnt[a:b]# main i/o pcirst# high-z high high high off off irdy#, trdy# main i/o pcirst# high-z high-z high-z high-z off off par main i/o pcirst# high-z undefined defined defined off off pcirst# resume i/o rsmrst# low high high high low low perr# main i/o pcirst# high-z high-z high-z high-z off off plock# main i/o pcirst# high-z high-z high-z high-z off off stop# main i/o pcirst# high-z high-z high-z high-z off off lpc interface lad[3:0] main i/o pcirst# high high high defined off off lframe# main i/o pcirst# high high high high off off lan connect and eeprom interface ee_cs lan i/o rsm_pwrok (ich2) lan_pwrok (ich2-m) low running defined defined note 4 note 4 ee_dout lan i/o rsm_pwrok (ich2) lan_pwrok (ich2-m) high running defined defined note 4 note 4 ee_shclk lan i/o rsm_pwrok (ich2) lan_pwrok (ich2-m) low running defined defined note 4 note 4 lan_rstsync lan i/o rsm_pwrok (ich2) lan_pwrok (ich2-m) high defined defined defined note 4 note 4 lan_txd[2:0] lan i/o rsm_pwrok (ich2) lan_pwrok (ich2-m) low defined defined defined note 4 note 4 power planes and pin states 3-4 82801BA ich2 and 82801BAm ich2-m datasheet ide interface pda[2:0], sda[2:0] main i/o pcirst# low undefined undefined driven off off pdcs1#, pdcs3# main i/o pcirst# high high high high off off pdd[15:0], sdd[15:0] main i/o pcirst# high-z high-z defined high-z off off pddack#, sddack# main i/o pcirst# high high high off off off pdior#, pdiow# main i/o pcirst# high high high off off off sdcs1#, sdcs3# main i/o pcirst# high high high off off off sdior#, sdiow# main i/o pcirst# high high high off off off interrupts pirq[a:h]# main i/o pcirst# high-z high-z defined high-z off off serirq main i/o pcirst# high-z high-z running high-z off off apicd[1:0] main i/o pcirst# high-z high-z running high-z off off usb interface usbp[3:0][p:n] resume i/o rsmrst# high-z high-z high-z high-z high-z high-z power management cpuperf# (ich2-m) main i/o pcirst# high-z high-z defined defined off off c3_stat# / gpio[21] (ich2-m) main i/o pcirst# high high low low off off ssmuxsel (ich2-m) main i/o pcirst# low low defined defined off off slp_s1# (ich2-m) main i/o pcirst# high high high low low low slp_s3# resume i/o rsmrst# high high high high low low slp_s5# resume i/o rsmrst# high high high high high low stp_pci# (ich2-m) main i/o pcirst# high high defined low low low stp_cpu# (ich2-m) main i/o pcirst# high high low low low low sus_stat# resume i/o rsmrst# high high low low low susclk resume i/o rsmrst# running processor interface a20m# cpu i/o pcirst# see note 1 high defined high off off cpupwrgd main i/o pcirst# see note 3 high-z high-z high-z off off cpuslp# cpu i/o pcirst# high high high defined (ich2) low (ich2-m) off off ignne# cpu i/o pcirst# see note 1 high high high off off init# cpu i/o pcirst# high high high high off off intr cpu i/o pcirst# see note 1 low defined low off off nmi cpu i/o pcirst# see note 1 low defined low off off smi# cpu i/o pcirst# high high defined high off off stpclk# cpu i/o pcirst# high high low low off off table 3-4. power plane and states for output and i/o signals (continued) signal name power plane reset signal during reset immediately after reset c3 (ich2-m) s1 s3 s4/s5 82801BA ich2 and 82801BAm ich2-m datasheet 3-5 power planes and pin states . smbus interface smbclk, smbdata resume i/o rsmrst# high-z high-z defined defined defined defined system management interface smlink[1:0] resume i/o rsmrst# high-z high-z defined defined defined defined miscellaneous signals spkr main i/o pcirst# high-z with internal pull-up low defined defined off off ac?97 interface ac_rst# resume i/o rsmrst# low low high cold reset bit (high) low low ac_sdout main i/o pcirst# low running running low off off ac_sync main i/o pcirst# low running running low off off unmuxed gpio signals gpio[18] (ich2) main i/o pcirst# high see note 2 ? defined off off gpio[19:20] (ich2) main i/o pcirst# high high ? defined off off gpio[21] (ich2) main i/o pcirst# high high ? defined off off gpio[22] (ich2) main i/o pcirst# high-z high-z ? defined off off gpio[23] (ich2) main i/o pcirst# low low ? defined off off gpio[24] (ich2) resume i/o rsmrst# high-z high ? defined defined defined gpio[25] resume i/o rsmrst# high-z high defined defined defined defined gpio[27:28] resume i/o rsmrst# high-z high defined defined defined defined table 3-4. power plane and states for output and i/o signals (continued) signal name power plane reset signal during reset immediately after reset c3 (ich2-m) s1 s3 s4/s5 notes: 1. ich2 and ich2-m: the ich2/ich2-m sets these signals at reset for processor frequency strap. 2. ich2 and ich2-m: gpio[18] will toggle at a frequency of approximately 1 hz when the ich2 comes out of reset 3. ich2 and ich2-m: cpupwrgd is an open-drain output that represents a logical and of the ich2?s vrmpwrgd (vgate / vrmpwrgd for the ich2-m) and pwrok signals and, thus, are driven low by ich2/ich2-m when either vrmpwrgd (vgate / vrmpwrgd for the ich2-m) or pwrok are inactive. during boot, or during a hard reset with power cycling, cpupwrgd will be expected to transition from low to high-z. 4. ich2-m only: lan connect and eeprom signals will either be "defined" or "off" in s3?s5 states depending on whether or not the lan power planes are active. 5. gpio[24:25, 27:28] for the ich2 and gpio[25, 27:28] for the 82801BAm ich2-m: these signals remain tri-stated for up to 110 ms after rsmrst# deassertion. at this point, they will be driven to their default (high) state. power planes and pin states 3-6 82801BA ich2 and 82801BAm ich2-m datasheet 3.5 power planes for input signals table 3-5 shows the power plane associated with each input signal, as well as what device drives the signal at various times. valid states include: ? high ? low ? static: will be high or low, but will not change ? driven: will be high or low, and is allowed to change ? running: for input clocks table 3-5. power plane for input signals signal name power well driver during reset c3 (ich2-m) s1 s3 s5 batlow# (ich2-m) resume i/o power supply high high high high a20gate main i/o external microcontroller static static low low ac_bit_clk main i/o ac?97 codec driven low low low ac_sdin[1:0] resume i/o ac?97 codec driven low low low agpbusy# (ich2-m) main i/o agp component driven high low low apicclk main i/o clock generator running low low low clk14 main i/o clock generator running low low low clk48 main i/o clock generator running low low low clk66 main logic clock generator running low low low ee_din lan i/o eeprom component driven driven note 1 note 1 ferr# main i/o cpu static static low low intruder# rtc external switch driven driven driven driven irq[15:14] main i/o ide driven static low low lan_clk lan i/o lan connect component driven driven note 1 note 1 rsm_pwrok (ich2) lan_pwrok (ich2-m) resume i/o external rc circuit (ich2) power supply (ich2-m) high high static static lan_rxd[2:0] lan i/o lan connect component driven driven note 1 note 1 ldrq[0]# main i/o lpc devices driven high low low ldrq[1]# main i/o lpc devices driven high low low oc[3:0]# resume i/o external pull-ups driven driven driven driven pciclk main i/o clock generator running low low low pddreq main i/o ide device driven static low low piordy main i/o ide device static static low low pme# resume i/o internal pull-up driven driven driven driven pwrbtn# resume i/o internal pull-up driven driven driven driven pwrok main i/o system power supply driven driven low low rcin# main i/o external microcontroller high high low low req[0:5]# main i/o pci master driven driven low low req[b:a]# main i/o pc/pci devices driven driven low low 82801BA ich2 and 82801BAm ich2-m datasheet 3-7 power planes and pin states . ri# resume i/o serial port buffer driven driven driven driven rsmrst# rtc external rc circuit high high high high rtcrst# rtc external rc circuit high high high high sddreq main i/o ide drive driven static low low serr# main i/o pci bus peripherals driven high low low siordy main i/o ide drive driven static low low smbalert# resume i/o external pull-up driven driven driven driven thrm# main i/o thermal sensor driven driven low low vrmpwrgd (ich2) main i/o cpu voltage regulator driven high low low vgate / vrmpwrgd (ich2-m) main i/o cpu voltage regulator driven high low low table 3-5. power plane for input signals (continued) signal name power well driver during reset c3 (ich2-m) s1 s3 s5 notes: 1. lan connect and eeprom signals will either be "driven" or "low" in s3?s5 states depending upon whether or not the lan power planes are active. power planes and pin states 3-8 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank 82801BA ich2 and 82801BAm ich2-m datasheet 4-1 system clock domains system clock domains 4 table 4-1 shows the system clock domains. figure 4-2 shows the assumed connection of the various system components, including the clock generator. for complete details of the system clocking solution, refer to the system?s clock generator component specification. figure 4-1. ich2 and system clock domains clock domain frequency source usage ich2 clk66 66 mhz main clock generator hub interface, processor interface. agp. 82801BA ich2: it is shut off during s3 or below. 82801BAm ich2-m: it is shut off during s1 or below. ich2 pciclk 33 mhz main clock generator free-running pci clock to ich2/ich2-m. 82801BA ich2: this clock remains on during s0 and s1 state, and is expected to be shut off during s3 or below. 82801BAm ich2-m: this clock remains on during s0 state, and is expected to be shut off during s1 or below. system pci 33 mhz main clock generator pci bus, lpc i/f. these only go to external pci and lpc devices. 82801BAm ich2-m: these will stop based on clkrun# (and stp_pci#) ich2 clk48 48 mhz main clock generator super i/o, usb controller. 82801BA ich2: expected to be shut off during s3 or below. 82801BAm ich2-m: expected to be shut off during s1 or below. ich2 clk14 14.31818 mhz main clock generator used for acpi timer. 82801BA ich2: expected to be shut off during s3 or below. 82801BAm ich2-m: expected to be shut off during s1 or below. ich2 ac_bit_clk 12.288 mhz ac?97 codec ac?97 link. generated by ac?97 codec. can be shut off by codec in d3. 82801BA ich2: expected to be shut off during s3 or below. 82801BAm ich2-m: expected to be shut off during s1 or below. rtc 32.768 khz ich2 rtc, power management. ich2 has its own oscillator. always running, even in g3 state. ich2 apicclk 33.33 mhz main clock generator used for ich2/ich2-m processor interrupt messages. runs at 33.33 mhz. 82801BA ich2: expected to be shut off during s3 or below. 82801BAm ich2-m: expected to be shut off during s1 or below. lan_clk 0.8 to 50 mhz lan connect component generated by the lan connect component. 82801BA ich2: expected to be shut off during s3 or below. 82801BAm ich2-m: expected to be shut off during s1 or below. system clock domains 4-2 82801BA ich2 and 82801BAm ich2-m datasheet figure 4-2. conceptual system clock diagram (82801BA ich2 and 82801BAm ich2-m) pci clocks (33 mhz) 66 mhz 14.31818 mhz 48 mhz hclock(s) (66/100/133 mhz) hclock (66/100/133 mhz) 33 mhz 14.31818 mhz stp_cpu# (ich2-m only) agp clock (66 mhz) apic clk 12.288 mhz processor(s) host controller ich2 agp rdram clock generator memory clock generator 50 mhz lan connect ac'97 codec(s) 2 2 or 3 agp clock (66 mhz) 32 khz xtal susclk# (32 khz) 48 mhz stp_pci# (ich2-m only) slp_s1# (ich2-m only) 82801BA ich2 and 82801BAm ich2-m datasheet 5-1 functional description functional description 5 5.1 hub interface to pci bridge (d30:f0) the hub interface to pci bridge resides in pci device 30, function 0 on bus #0. this portion of the ich2 implements the buffering and control logic between pci and the hub interface. the arbitration for the pci bus is handled by this pci device. the pci decoder in this device must decode the ranges for the hub interface. all register contents will be lost when core well power is removed. 5.1.1 pci bus interface the ich2 pci interface provides a 33 mhz, rev. 2.2 compliant implementation. all pci signals are 5v tolerant. the ich2 integrates a pci arbiter that supports up to six external pci bus masters in addition to the internal ich2 requests. note that most transactions targeted to the ich2 will first appear on the external pci bus before being claimed back by the ich2. the exceptions are i/o cycles involving usb, ide, and ac?97. these transactions will complete over the hub interface without appearing on the external pci bus. configuration cycles targeting usb, ide or ac?97 will appear on the pci bus. if the ich2 is programmed for positive decode, the ich2 will claim the cycles appearing on the external pci bus in medium decode time. if the ich2 is programmed for subtractive decode, the ich2 will claim these cycles in subtractive time. if the ich2 is programmed for subtractive decode, these cycles can be claimed by another positive decode agent out on pci. this architecture enables the ability to boot off of a pci card that positively decodes the boot cycles. to boot off a pci card it is necessary to keep the ich2 in subtractive decode mode. when booting off a pci card, the boot_sts bit (bit 2, tco2 status register) will be set. note: the ich2?s ac?97, ide, and usb controllers can not access pci address ranges. note: pci devices that cause long latencies (numerous retries) to processor-to-pci locked cycles may starve isochronous transfers between usb or ac?97 devices and memory. this will result in overrun or underrun, causing reduced quality of the isochronous data (e.g., audio). note: pci configuration write cycles, initiated by the processor, with the following characteristics will be converted to a special cycle with the shutdown message type. ? device number (ad[15:11]) = ?11111? ? function number (ad[10:8]) = ?111? ? register number (ad[7:2]) = ?000000? ? data = 00h ? bus number matches secondary bus number f or the 82801BAm ich2-m, devices on the ich2-m pci bus (other than the ich2-m) are not p ermitted to assert the plock# signal. functional description 5-2 82801BA ich2 and 82801BAm ich2-m datasheet note: if the processor issues a locked cycle to a resource that is too slow (e.g., pci), the ich2 will not allow upstream requests to be performed until the cycle completion. this may be critical for isochronous buses that assume certain timing for their data flow (e.g., ac?97 or usb). devices on these buses may suffer from underrun if the asynchronous traffic is too heavy. underrun means that the same data is sent over the bus while ich2 is not able to issue a request for the next data. snoop cycles are not permitted while the front side bus is locked. note: locked cycles are assumed to be rare. locks by pci targets are assumed to exist for a short duration (a few microseconds at most). if a system has a very large number of locked cycles and some that are very long, the system will definitely experience underruns and overruns. the units most likely to have problems are the ac'97 controller and the usb controller. other units could get underruns/overruns, but are much less likely. the ide controller (due to its stalling capability on the cable) should not get any underruns or overruns. note: the ich2 was designed to provide high performance support to pci peripherals using its data prefetch capabilities. if a pci master is burst reading and is disconnected by the ich2 to pre-fetch the requested cache line, the ich2 will delay transaction the cycle while it prefetches more data, and give the bus to another agent. once the bus is given back to this bus master, if it does not return with the successive previously requested read address, which was prefetched by the ich2, the ich2 will keep retrying the bus master until either it comes back for the prefetched data, or the delayed transaction discard timer expires (1024 pci clocks) before discarding this prefetched data and servicing the request. this induces long latencies to pci bus masters that behave this way. to reduce this latency, the discard timer mode bit (d30:f0;cnf(50-51h):[bit-2]) can be set to 1. this will reduce the discard timer from 1024 pci clocks (32 us) to 128 clocks (4 us) and improve latency for masters with this behavior. 5.1.2 pci-to-pci bridge model from a software perspective, the ich2 contains a pci-to-pci bridge. this bridge connects the hub interface to the pci bus. by using the pci-to-pci bridge software model, the ich2 can have its decode ranges programmed by existing plug-and-play software such that pci ranges do not conflict with agp and graphics aperture ranges in the host controller. 5.1.3 idsel to device number mapping when addressing devices on the external pci bus (with the pci slots), the ich2 asserts one address signal as an idsel. when accessing device 0, the ich2 asserts ad16. when accessing device 1, the ich2 asserts ad17. this mapping continues up to device 15 where the ich2 asserts ad31. note that the ich2?s internal functions (ac?97, ide, usb, and pci bridge) are enumerated like they are on a separate pci bus (the hub interface) from the external pci bus. the integrated lan controller is device 8 on the ich2?s pci bus and, hence, uses ad24 for idsel 5.1.4 serr# functionality there are several internal and external sources that can cause serr#. the ich2 can be programmed to cause an nmi based on detecting that an serr# condition has occurred. the nmi can also be routed to, instead, cause an smi#. note that the ich2 does not drive the external pci bus serr# signal active onto the pci bus. the external serr# signal is an input into the ich2 driven only by external pci devices. the conceptual logic diagrams in figure 5-1 and figure 5-2 illustrate all sources of serr#, along with their respective enable and status bits. figure 5-3 shows how the ich2 error reporting logic is configured for nmi# generation. 82801BA ich2 and 82801BAm ich2-m datasheet 5-3 functional description figure 5-1. primary device status register error reporting logic figure 5-2. secondary status register error reporting logic and or and d30:f0 bridge_cnt [parity error response enable] d30:f0 bridge_cnt [serr# enable] pci address parity error d30:f0 cmd [serr_en] d30:f0 pd_sts [sse] and and and and or delayed transaction timeout d30:f0 err_cmd [serr_dtt_en] serr# pin d30:f0 bridge_cnt [serr# enable] d30:f0 err_cmd [serr_rta_en] received target abort d30:f0 err_sts [serr_dtt] d30:f0 cmd [serr_en] d30:f0 err_sts [serr_rta] and or and and d30:f0 secsts [sse] d30:f0 bridge_cnt [serr# enable] pci delayed transaction timeout d31:f0 d31_err_cfg [serr_dtt_en] lpc device signaling an error iochk# via serirq tco1_sts [huberr_sts] d31:f0 d31_err_cfg [serr_rta_en] received target abort functional description 5-4 82801BA ich2 and 82801BAm ich2-m datasheet 5.1.5 parity error detection the ich2 can detect and report different parity errors in the system. the ich2 can be programmed to cause an nmi (or smi# if nmi is routed to smi#) based on detecting a parity error. the conceptual logic diagram in figure 5-3 details all the parity errors that the ich2 can detect, along with their respective enable bits, status bits, and the results. note: if nmis are enabled and parity error checking on pci is also enabled, then parity errors cause an nmi. some operating systems will not attempt to recover from this nmi, since it considers the detection of a pci error to be a catastrophic event. figure 5-3. nmi# generation logic and iochk from serirq logic nmi_sc [iochk_nmi_en] and to nmi# output and gating logic or nmi_sc [iochk_nmi_sts] and nmi_sc [serr#_nmi_sts] nmi_sc [pci_serr_en] or d30:f0 secsts [sse] d30:f0 pdsts [sse] or and or tco1_sts [hubnmi_sts] tco1_cnt [nmi_now] nmi_en [nmi_en] d30:f0 pd_sts [dpd] d30:f0 secsts [dpd] pci parity error detected during ac'97, ide or usb master cycle d30:f0 bridge_cnt [parity error response enable] and d31:f0 pcista [dped] pci parity error detected during lpc or legacy dma master cycle d31:f0 pcicmd [per] and hub interface parity error detected d30:f0 cmd [parity error response] 82801BA ich2 and 82801BAm ich2-m datasheet 5-5 functional description 5.1.6 standard pci bus configuration mechanism the pci bus defines a slot based ?configuration space? that allows each device to contain up to 8 functions with each function containing up to 256 8-bit configuration registers. the pci specification defines two bus cycles to access the pci configuration space: configuration read and configuration write. memory and i/o spaces are supported directly by the processor. configuration space is supported by a mapping mechanism implemented within the ich2. the pci specification defines two mechanisms to access configuration space (mechanism #1 and mechanism #2). the ich2 only supports mechanism #1. configuration cycles for pci bus #0 devices #2 through #31, and for pci bus numbers greater than 0 will be sent towards the ich2 from the host controller. the ich2 compares the non-zero bus number with the secondary bus number and subordinate bus number registers of its p2p bridge to determine if the configuration cycle is meant for primary pci or a downstream pci bus. type 0 to type 0 forwarding when a type 0 configuration cycle is received on the hub interface, the ich2 forwards these cycles to pci and then reclaims them. the ich2 uses address bits ad[15:14] to communicate the ich2 device numbers in type 0 configuration cycles. if the type 0 cycle on the hub interface specifies any device number other than 30 or 31, the ich2 will not set any address bits in the range ad[31:11] during the corresponding transaction on pci. table 5-1 shows the device number translation. the ich2 logic generates single dword configuration read and write cycles on the pci bus. the ich2 generates a type 0 configuration cycle for configurations to the bus number matching the pci bus. type 1 configuration cycles are converted to type 0 cycles in this case. if the cycle is targeting a device behind an external bridge, the ich2 runs a type 1 cycle on the pci bus. type 1 to type 0 conversion when the bus number for the type 1 configuration cycle matches the pci (secondary) bus number, the ich2 converts the address as follows: ? for device numbers 0 through 15, only one bit of the pci address [31:16] is set. if the device number is 0, ad[16] is set; if the device number is 1, ad[17] is set; etc. ? the ich2 always drives 0s on bits ad[15:11] when converting type 1 configurations cycles to type 0 configuration cycles on pci. ? address bits [10:1] are also passed unchanged to pci. ? address bit [0] is changed to 0. table 5-1. type 0 configuration cycle device number translation device # in hub interface type 0 cycle ad[31:11] during address phase of type 0 cycle on pci 0 through 29 0000000000000000_00000b 30 0000000000000000_01000b 31 0000000000000000_10000b functional description 5-6 82801BA ich2 and 82801BAm ich2-m datasheet 5.1.7 pci dual address cycle (dac) support (82801BA ich2 only) 5.2 lan controller (b1:d8:f0) the ich2?s integrated lan controller includes a 32-bit pci controller that provides enhanced scatter-gather bus mastering capabilities and enables the lan controller to perform high speed data transfers over the pci bus. its bus master capabilities enable the component to process high level commands and perform multiple operations, which lowers processor utilization by off- loading communication tasks from the processor. two large transmit and receive fifos of 3 kb each help prevent data underruns and overruns while waiting for bus accesses. this enables the integrated lan controller to transmit data with minimum interframe spacing (ifs). the ich2 integrated lan controller can operate in either full duplex or half duplex mode. in full duplex mode the lan controller adheres with the ieee 802.3x flow control specification. half duplex performance is enhanced by a proprietary collision reduction mechanism. the integrated lan controller also includes an interface to a serial (4-pin) eeprom. the eeprom provides power-on initialization for hardware and software configuration parameters. from a software perspective, the integrated lan controller appears to reside on the secondary side of the ich2?s virtual pci-to-pci bridge (see section 5.1.2 ). this is typically bus 1; it may be assigned a different number depending on system configuration. the 82801BA ich2 supports dual address cycle (dac) format on pci for cycles from pci initiators to main memory. this allows pci masters to generate an address up to 44 bits. the size of the actual supported memory space will be determined by the memory controller and the p rocessor. the dac mode is only supported for pci adapters and is not supported for any of the internal pci masters (ide, lan, usb, ac?97, 8237 dma, etc.). ich2 does not support dac for processor- initiated cycles. when a pci master wants to initiate a cycle with an address above 4 gb, it follows the following b ehavioral rules (see pci 2.2 specification, section 3.9 for more details): 1. on the first clock of the cycle (when frame# is first active), the peripheral uses the dac encoding on the c/be# signals. this unique encoding is 1101. 2. also during the first clock, the peripheral drives the ad[31:0] signals with the low address. 3. on the second clock, the peripheral drives ad[31:0] with the high address. the address is right justified: a[43:32] appear on ad[12:0]. the value of ad[31:13] is expected to be 0, however the ich2 will ignore these bits. c/be# indicate the bus command type (memory read, memory write, etc.) 4. the rest of the cycle proceeds normally. 82801BA ich2 and 82801BAm ich2-m datasheet 5-7 functional description feature summary ? compliance with advanced configuration and power interface and pci power management standards ? support for wake-up on interesting packets and link status change ? support for remote power-up using wake on lan* (wol) technology ? deep power-down mode support ? support of wired for management (wfm) rev 2.0 ? backward compatible software with 82557, 82558 and 82559 ? tcp/udp checksum offload capabilities ? support for intel?s adaptive technology 5.2.1 lan controller architectural overview figure 5-4 is a high level block diagram of the ich2 integrated lan controller. it is divided into four main subsystems: a parallel subsystem, a fifo subsystem and the carrier-sense multiple access with collision detect (csma/cd) unit. parallel subsystem overview the parallel subsystem is divided into several functional blocks: a pci bus master interface, a micromachine processing unit and its corresponding microcode rom, and a pci target control/ eeprom/ interface. the parallel subsystem also interfaces to the fifo subsystem, passing data (e.g., transmit, receive, and configuration data) and command and status parameters between these two blocks. the pci bus master interface provides a complete interface to the pci bus and is compliant with the pci bus specification, revision 2.2. the lan controller provides 32 bits of addressing and data, as well as the complete control interface to operate on the pci bus. as a pci target, it follows the pci configuration format which allows all accesses to the lan controller to be automatically mapped into free memory and i/o space upon initialization of a pci system. for processing of transmit and receive frames, the integrated lan controller operates as a master on the pci bus, initiating zero wait state transfers for accessing these data parameters. figure 5-4. integrated lan controller block diagram csma/cd unit data interface unit (diu) four channel addressing unit - dma pci bus interface unit (biu) pci target and eeprom interface micro- machine dual ported fifo 3 kbyte rx fifo fifo control 3 kbyte tx fifo eeprom interface pci interface lan connect interface functional description 5-8 82801BA ich2 and 82801BAm ich2-m datasheet the lan controller control/status register block is part of the pci target element. the control/ status register block consists of the following lan controller internal control registers: system control block (scb), port, eeprom control and management data interface (mdi) control. the micromachine is an embedded processing unit contained in the lan controller that enables adaptive technology. the micromachine accesses the lan controller?s microcode rom, working its way through the opcodes (or instructions) contained in the rom to perform its functions. parameters accessed from memory (e.g., pointers to data buffers) are also used by the micromachine during the processing of transmit or receive frames by the lan controller. a typical micromachine function is to transfer a data buffer pointer field to the lan controller?s dma unit for direct access to the data buffer. the micromachine is divided into two units, receive unit and command unit that includes transmit functions. these two units operate independently and concurrently. control is switched between the two units according to the microcode instruction flow. the independence of the receive and command units in the micromachine allows the lan controller to execute commands and receive incoming frames simultaneously, with no real-time processor intervention. the lan controller contains an interface to an external serial eeprom. the eeprom is used to store relevant information for a lan connection such as node address, as well as board manufacturing and configuration information. both read and write accesses to the eeprom are supported by the lan controller. information on the eeprom interface is detailed in section 5.2.4 . fifo subsystem overview the ich2 lan controller fifo subsystem consists of a 3 kb transmit fifo and 3 kb receive fifo. each fifo is unidirectional and independent of the other. the fifo subsystem serves as the interface between the lan controller parallel side and the serial csma/cd unit. it provides a temporary buffer storage area for frames as they are either being received or transmitted by the lan controller, which improves performance: ? transmit frames can be queued within the transmit fifo, allowing back-to-back transmission within the minimum interframe spacing (ifs). ? the storage area in the fifo allows the lan controller to withstand long pci bus latencies without losing incoming data or corrupting outgoing data. ? the ich2 lan controller?s transmit fifo threshold allows the transmit start threshold to be tuned to eliminate underruns while concurrent transmits are being performed. ? the fifo subsection allows extended pci zero wait state burst accesses to or from the lan controller for both transmit and receive frames since the transfer is to the fifo storage area rather than directly to the serial link. ? transmissions resulting in errors (collision detection or data underrun) are retransmitted directly from the lan controller?s fifo, increasing performance and eliminating the need to re-access this data from the host system. ? incoming runt receive frames (in other words, frames that are less than the legal minimum frame size) can be discarded automatically by the lan controller without transferring this faulty data to the host system. serial csma/cd unit overview the csma/cd unit of the ich2 lan controller allows it to be connected to the 82562et/em 10/100 mbps ethernet lan connect components or the 82562eh 1 mbps homepna*-compliant lan connect component. the csma/cd unit performs all of the functions of the 802.3 protocol such as frame formatting, frame stripping, collision handling, deferral to link traffic, etc. the csma/cd unit can also be placed in a full duplex mode which allows simultaneous transmission and reception of frames. 82801BA ich2 and 82801BAm ich2-m datasheet 5-9 functional description 5.2.2 lan controller pci bus interface as a fast ethernet controller, the role of the ich2 integrated lan controller is to access transmitted data or deposit received data. the lan controller, as a bus master device, initiates memory cycles via the pci bus to fetch or deposit the required data. to perform these actions, the lan controller is controlled and examined by the processor via its control and status structures and registers. some of these control and status structures reside in the lan controller and some reside in system memory. for access to the lan controller?s control/ status registers (csr), the lan controller acts as a slave (in other words, a target device). the lan controller serves as a slave also while the processor accesses the eeprom. 5.2.2.1 bus slave operation the ich2 integrated lan controller serves as a target device in one of the following cases: ? processor accesses to the lan controller system control block (scb) control/status registers (csr) ? processor accesses to the eeprom through its csr ? processor accesses to the lan controller port address via the csr ? processor accesses to the mdi control register in the csr ? pci configuration cycles the size of the csr memory space is 4 kb in the memory space and 64 bytes in the i/o space. the lan controller treats accesses to these memory spaces differently. control/status register (csr) accesses the integrated lan controller supports zero wait state single cycle memory or i/o mapped accesses to its csr space. separate bars request 4 kb of memory space and 64 bytes of i/o space to accomplish this. based on its needs, the software driver uses either memory or i/o mapping to access these registers. the lan controller provides 4 kb of csr space, which includes the following elements: ? system control block (scb) registers ? port register ? eeprom control register ? mdi control register ? flow control registers in the case of accessing the control/status registers, the processor is the initiator and the lan controller is the target. read accesses: the processor, as the initiator, drives address lines ad[31:0], the command and byte enable lines c/be[3:0]#, and the control lines irdy# and frame#. as a slave, the lan controller controls the trdy# signal and provides valid data on each data access. the lan controller allows the processor to issue only one read cycle when it accesses the control/status registers, generating a disconnect by asserting the stop# signal. the processor can insert wait states by deasserting irdy# when it is not ready. functional description 5-10 82801BA ich2 and 82801BAm ich2-m datasheet write accesses: the processor, as the initiator, drives the address lines ad[31:0], the command and byte enable lines c/be[3:0]#, and the control lines irdy# and frame#. it also provides the lan controller with valid data on each data access immediately after asserting irdy#. the lan controller controls the trdy# signal and asserts it from the data access. the lan controller allows the processor to issue only one i/o write cycle to the control/status registers, generating a disconnect by asserting the stop# signal. this is true for both memory mapped and i/o mapped accesses. retry premature accesses the lan controller responds with a retry to any configuration cycle accessing the lan controller before the completion of the automatic read of the eeprom. the lan controller may continue to retry any configuration accesses until the eeprom read is complete. the lan controller does not enforce the rule that the retried master must attempt to access the same address again to complete any delayed transaction. any master access to the lan controller after the completion of the eeprom read will be honored. error handling data parity errors: the lan controller checks for data parity errors while it is the target of the transaction. if an error was detected, the lan controller always sets the detected parity error bit in the pci configuration status register, bit 15. the lan controller also asserts perr#, if the parity error response bit is set (pci configuration command register, bit 6). the lan controller does not attempt to terminate a cycle in which a parity error was detected. this gives the initiator the option of recovery. target-disconnect: the lan controller terminates a cycle in the following cases: ? after accesses to its csr ? after accesses to the configuration space system error: the lan controller reports parity error during the address phase using the serr# pin. if the serr# enable bit in the pci configuration command register or the parity error response bit are not set, the lan controller only sets the detected parity error bit (pci configuration status register, bit 15). if serr# enable and parity error response bits are both set, the lan controller sets the signaled system error bit (pci configuration status register, bit 14) as well as the detected parity error bit and asserts serr# for one clock. the lan controller, when detecting system error, will claim the cycle if it was the target of the transaction and continue the transaction as if the address was correct. note: the lan controller reports a system error for any error during an address phase, whether or not it is involved in the current transaction. 5.2.2.2 bus master operation as a pci bus master, the ich2 integrated lan controller initiates memory cycles to fetch data for transmission or deposit received data and for accessing the memory resident control structures. the lan controller performs zero wait state burst read and write cycles to the host main memory. for bus master cycles, the lan controller is the initiator and the host main memory (or the pci host bridge, depending on the configuration of the system) is the target. the processor provides the lan controller with action commands and pointers to the data buffers that reside in host main memory. the lan controller independently manages these structures and initiates burst memory cycles to transfer data to and from them. the lan controller uses the 82801BA ich2 and 82801BAm ich2-m datasheet 5-11 functional description memory read multiple (mr multiple) command for burst accesses to data buffers and the memory read line (mr line) command for burst accesses to control structures. for all write accesses to the control structure, the lan controller uses the memory write (mw) command. for write accesses to the data structure, the lan controller may use either the memory write or memory write and invalidate (mwi) commands. read accesses: the lan controller performs block transfers from host system memory to perform frame transmission on the serial link. in this case, the lan controller initiates zero wait state memory read burst cycles for these accesses. the length of a burst is bounded by the system, the lan controller?s internal fifo. the length of a read burst may also be bounded by the value of the transmit dma maximum byte count in the configure command. the transmit dma maximum byte count value indicates the maximum number of transmit dma pci cycles that will be completed after a lan controller internal arbitration. the lan controller, as the initiator, drives the address lines ad[31:0], the command and byte enable lines c/be[3:0]#, and the control lines irdy# and frame#. the lan controller asserts irdy# to support zero wait state burst cycles. the target signals the lan controller that valid data is ready to be read by asserting the trdy# signal. write accesses: the lan controller performs block transfers to host system memory during frame reception. in this case, the lan controller initiates memory write burst cycles to deposit the data, usually without wait states. the length of a burst is bounded by the system and the lan controller?s internal fifo threshold. the length of a write burst may also be bounded by the value of the receive dma maximum byte count in the configure command. the receive dma maximum byte count value indicates the maximum number of receive dma pci transfers that will be completed before the lan controller internal arbitration. the lan controller, as the initiator, drives the address lines ad[31:0], the command and byte enable lines c/be[3:0]#, and the control lines irdy# and frame#. the lan controller asserts irdy# to support zero wait state burst cycles. the lan controller also drives valid data on ad[31:0] lines during each data phase (from the first clock and on). the target controls the length and signal?s completion of a data phase by deassertion and assertion of trdy#. cycle completion: the lan controller completes (terminates) its initiated memory burst cycles in the following cases: ? normal completion: all transaction data has been transferred to or from the target device (for example, host main memory). ? backoff: latency timer has expired and the bus grant signal (gnt#) was removed from the lan controller by the arbiter, indicating that the lan controller has been preempted by another bus master. ? transmit or receive dma maximum byte count: the lan controller burst has reached the length specified in the transmit or receive dma maximum byte count field in the configure command block. ? target termination: the target may request to terminate the transaction with a target- disconnect, target-retry, or target-abort. in the first two cases, the lan controller initiates the cycle again. in the case of a target-abort, the lan controller sets the received target-abort bit in the pci configuration status field (pci configuration status register, bit 12) and does not re-initiate the cycle. ? master abort: the target of the transaction has not responded to the address initiated by the lan controller (in other words, devsel# has not been asserted). the lan controller simply deasserts frame# and irdy# as in the case of normal completion. ? error condition: in the event of parity or any other system error detection, the lan controller completes its current initiated transaction. any further action taken by the lan controller depends on the type of error and other conditions. functional description 5-12 82801BA ich2 and 82801BAm ich2-m datasheet memory write and invalidate the lan controller has four direct memory access (dma) channels. of these four channels (the receive dma channel) is used to deposit the large number of data bytes received from the link into system memory. the receive dma uses both the memory write (mw) and the memory write and invalidate (mwi) commands. to use mwi, the lan controller must guarantee the following: 1. minimum transfer of one cache line 2. active byte enable bits (or be[3:0]# are all low) during mwi access 3. the lan controller may cross the cache line boundary only if it intends to transfer the next cache line too. to ensure the above conditions, the lan controller may use the mwi command only under the following conditions: 1. the cache line size (cls) written in the cls register during pci configuration is 8 or 16 dwords. 2. the accessed address is cache line aligned. 3. the lan controller has at least 8 or 16 dwords of data in its receive fifo. 4. there are at least 8 or 16 dwords of data space left in the system memory buffer. 5. the mwi enable bit in the pci configuration command register, bit 4, should is set to 1. 6. the mwi enable bit in the lan controller configure command should is set to 1. if any one of the above conditions does not hold, the lan controller will use the mw command. if a mwi cycle has started and one of the conditions is no longer valid (for example, the data space in the memory buffer is now less than cls), then the lan controller terminates the mwi cycle at the end of the cache line. the next cycle will be either a mw or mwi cycle depending on the conditions listed above. if the lan controller started a mw cycle and reached a cache line boundary, it either continues or terminates the cycle depending on the terminate write on cache line configuration bit of the lan controller configure command (byte 3, bit 3). if this bit is set, the lan controller terminates the mw cycle and attempts to start a new cycle. the new cycle is a mwi cycle if this bit is set and all of the above listed conditions are met. if the bit is not set, the lan controller continues the mw cycle across the cache line boundary if required. read align the read align feature enhances the lan controller?s performance in cache line oriented systems. in these particular systems, starting a pci transaction on a non-cache line aligned address may cause low performance. to resolve this performance anomaly, the lan controller attempts to terminate transmit dma cycles on a cache line boundary and start the next transaction on a cache line aligned address. this feature is enabled when the read align enable bit is set in the lan controller configure command (byte 3, bit 2). if this bit is set, the lan controller operates as follows: ? when the lan controller is almost out of resources on the transmit dma (i.e., the transmit fifo is almost full), it attempts to terminate the read transaction on the nearest cache line boundary when possible. ? when the arbitration counter?s feature is enabled (i.e., the transmit dma maximum byte count value is set in the configure command), the lan controller switches to other pending dmas on cache line boundary only. 82801BA ich2 and 82801BAm ich2-m datasheet 5-13 functional description note: this feature is not recommended for use in non-cache line oriented systems since it may cause shorter bursts and lower performance. note: this feature should be used only when the cls register in pci configuration space is set to 8 or 16. note: the lan controller reads all control data structures (including receive buffer descriptors) from the first dword (even if it is not required) to maintain cache line alignment. error handling data parity errors: as an initiator, the lan controller checks and detects data parity errors that occur during a transaction. if the parity error response bit is set (pci configuration command register, bit 6), the lan controller also asserts perr# and sets the data parity detected bit (pci configuration status register, bit 8). in addition, if the error was detected by the lan controller during read cycles, it sets the detected parity error bit (pci configuration status register, bit 15). 5.2.3 clockrun# signal (82801BAm ich2-m only) 5.2.3.1 pci power management enhanced support for the power management standard, pci specification rev. 2.2, is provided in the ich2 integrated lan controller. the lan controller supports a large set of wake-up packets and the capability to wake the system from a low power state on a link status change. the lan controller enables the host system to be in a sleep state and remain virtually connected to the network. after a power management event or link status change is detected, the lan controller will wake the host system. the sections below describe these events, the lan controller power states, and estimated power consumption at each power state. the ich2-m receives a free-running 33 mhz clock. it does not stop based on the clkrun# signal and protocol. when the lan controller runs cycles on the pci bus, the ich2-m makes sure that the stp_pci# signal is high indictating that the pci clock is running. this is to make sure that any pci tracker will not get confused by transactions on the pci bus with its pci clock stopped. functional description 5-14 82801BA ich2 and 82801BAm ich2-m datasheet power states the lan controller contains power management registers for pci and implements all four power states defined in the power management network device class reference specification, rev. 1.0. the four states, d0 through d3, vary from maximum power consumption at d0 to the minimum power consumption at d3. pci transactions are only allowed in the d0 state, except for host accesses to the lan controller?s pci configuration registers. the d1 and d2 power management states enable intermediate power savings while providing the system wake-up capabilities. in the d3 state, the lan controller can provide wake-up capabilities. wake-up indications from the lan controller are provided by the power management event (pme#) signal. ? d0 power state. as defined in the network device class reference specification, the device is fully functional in the d0 power state. in this state, the lan controller receives full power and should be providing full functionality. in the lan controller the d0 state is partitioned into two substates, d0 uninitialized (d0u) and d0 active (d0a). d0u is the lan controller?s initial power state following a pci rst#. while in the d0u state, the lan controller has pci slave functionality to support its initialization by the host and supports wake on lan* mode. initialization of the csr, memory, or i/o base address registers (pci configuration space) switches the lan controller from d0u state to d0a state. in the d0a state, the lan controller provides its full functionality and consumes its nominal power. in addition, the lan controller supports wake on link status change (see section 5.2.3.3 ). while it is active, the lan controller requires a nominal pci clock signal (in other words, a clock frequency greater than 16 mhz) for proper operation. the lan controller supports a dynamic standby mode. in this mode, the lan controller is able to save almost as much power as it does in the static power-down states. the transition to or from standby is done dynamically by the lan controller and is transparent to the software. ? d1 power state. for a device to meet the d1 power state requirements, as specified in the advanced configuration and power interface (acpi) specification, revision 1.0, it must not allow bus transmission or interrupts; however, bus reception is allowed. therefore, device context may be lost and the lan controller does not initiate any pci activity. in this state, the lan controller responds only to pci accesses to its configuration space and system wake-up events. the lan controller retains link integrity and monitors the link for any wake-up events such as wake-up packets or link status change. following a wake-up event, the lan controller asserts the pme# signal. ? d2 power state. the acpi d2 power state is similar in functionality to the d1 power state. in addition to d1 functionality, the lan controller can provide a lower power mode with wake- on-link status change capability. the lan controller may enter this mode if the link is down while the lan controller is in the d2 state. in this state, the lan controller monitors the link for a transition from an invalid to a valid link. the sub-10 ma state due to an invalid link can be enabled or disabled by the pme_en bit in the power management driver register (pmdr). the lan controller will consume in d2 10 ma regardless of the link status. it is the lan connect component that consumes much less power during link down, hence lan controller in this state can consume <10 ma. ? d3 power state. in the d3 power state, the lan controller has the same capabilities and consumes the same amount of power as it does in the d2 state. however, it enables the pci system to be in the b3 state. if the pci system is in the b3 state (in other words, no pci power is present), the lan controller provides wake-up capabilities. if pme is disabled, the lan controller does not provide wake-up capability or maintain link integrity. in this mode the lan controller consumes its minimal power (if pme_en=0). the lan controller enables a system to be in a sub-5 watt state (low power state) and still be virtually connected. more specifically, the lan controller supports full wake-up capabilities while it is in the d3 cold state. the lan controller is in the ich2 resume well and, thus, is connected to an auxiliary power source (a separate lan well). this enables it to provide wake-up functionality while the pci power is off. 82801BA ich2 and 82801BAm ich2-m datasheet 5-15 functional description 5.2.3.2 pci reset signal the pcirst# signal may be activated in one of the following cases: ? during s3-s5 states ? due to a cf9h reset if pme# is enabled (in the pci power management registers), pcirst# assertion does not affect any pme# related circuits (in other words, pci power management registers and the wake-up packet would not be affected). while pcirst# is active, the lan controller ignores other pci signals. the configuration of the lan controller registers associated with acpi wake events is not affected by pcirst#. the integrated lan controller uses the pcirst# or the pwrok signal as an indication to ignore the pci interface. following the deassertion of pcirst#, the lan controller pci configuration space, mac configuration, and memory structure are initialized while preserving the pme# signal and its context. 5.2.3.3 wake-up events there are two types of wake-up events: ?interesting? packets and link status change. these two events are detailed below. note: if the wol bit in the eeprom is not set, wake-up events are supported only if the pme enable bit in the power management control/status register (pmcsr) is set. however, if the wol bit in the eeprom is set, and wake on magic packet or wake on link status change are enabled, the power management enable bit is ignored with respect to these events. in the latter case, pme# would be asserted by these events. "interesting" packet event in the power-down state, the lan controller is capable of recognizing ?interesting? packets. the lan controller supports pre-defined and programmable packets that can be defined as any of the following: ? arp packets (with multiple ip addresses) ? direct packets (with or without type qualification) ? magic packet* ? neighbor discovery multicast address packet (?arp? in ipv6 environment) ? netbios over tcp/ip (nbt) query packet (under ipv4) ? internetwork package exchange* (ipx) diagnostic packet this allows the lan controller to handle various packet types. in general, the lan controller supports programmable filtering of any packet in the first 128 bytes. functional description 5-16 82801BA ich2 and 82801BAm ich2-m datasheet when the lan controller is in one of the low power states, it searches for a predefined pattern in the first 128 bytes of the incoming packets. the only exception is the magic packet, which is scanned for the entire frame. the lan controller will classify the incoming packets as one of the following categories: ? no match: the lan controller discards the packet and continues to process the incoming packets. ? wake-up packet: the lan controller is capable of recognizing and storing the first 128 bytes of a wake-up packet. if a wake-up packet is larger than 128 bytes, its tail is discarded by the lan controller. after the system is fully powered-up, software has the ability to determine the cause of the wake-up event via the pmdr and dump the stored data to the host memory. magic packets are an exception. the magic packets may cause a power management event and set an indication bit in the pmdr; however, it is not stored by the lan controller for use by the system when it is woken up. link status change event the lan controller link status indication circuit is capable of issuing a pme on a link status change from a valid link to an invalid link condition or vice versa. the lan controller reports a pme link status event in all power states. if the wol bit in the eeprom is not set, the pme# signal is gated by the pme enable bit in the pmcsr and the csma configure command. 5.2.3.4 wake on lan (preboot wake-up) the lan controller enters wol mode after reset if the wol bit in the eeprom is set. at this point, the lan controller is in the d0u state. when the lan controller is in wol mode: ? the lan controller scans incoming packets for a magic packet and asserts the pme# signal for 52 ms when a one is detected in wake on lan mode. ? the activity led changes its functionality to indicates that the received frame passed individual address (ia) filtering or broadcast filtering. ? the pci configuration registers are accessible to the host. the lan controller switches from wol mode to the d0a power state following a setup of the memory or i/o base address registers in the pci configuration space. 82801BA ich2 and 82801BAm ich2-m datasheet 5-17 functional description 5.2.4 serial eeprom interface the serial eeprom stores configuration data for the ich2 integrated lan controller and is a serial in/serial out device. the lan controller supports a 64 word size or 256 register size eeprom and automatically detects the eeprom?s size. a 256 word eeprom device is required for a cardbus system and contains the cis information. the eeprom should operate at a frequency of at least 1 mhz. all accesses, either read or write, are preceded by a command instruction to the device. the address field is six bits for a 64 word eeprom or eight bits for a 256 register eeprom. the end of the address field is indicated by a dummy zero bit from the eeprom, which indicates the entire address field has been transferred to the device. an eeprom read instruction waveform is shown in figure 5-5 . the lan controller performs an automatic read of seven words (0h, 1h, 2h, ah, bh, ch and dh) of the eeprom after the deassertion of reset. the ich2 integrated lan controller?s eeprom format is shown below in table 5-2 . for additional information, refer to application note ap-409, " i/o controller hub eeprom map and programming information " figure 5-5. 64-word eeprom read instruction waveform a 1 a 0 ee_cs ee_shclkk ee_din ee_dout a 5 a 4 a 2 d 15 d 0 read op code a 3 a 1 a 0 functional description 5-18 82801BA ich2 and 82801BAm ich2-m datasheet words 00h through 02h are used by the hardware and are common to all controllers. table 5-2. i/o control hub 2 eeprom address map word high byte (bits 15:8) low byte (bits 7:0) used by 00h ethernet individual address byte 2 ethernet individual address byte 1 hardware 01h ethernet individual address byte 4 ethernet individual address byte 3 hardware 02h ethernet individual address byte 6 ethernet individual address byte 5 hardware 03h compatibility byte 1 compatibility byte 0 intel ? driver 04h reserved 05h controller type (02 for ich2) connector type intel driver 06h phy device record 07h reserved 08h pwa number byte 4 pwa number byte 3 factory 09h pwa number byte 2 pwa number byte 1 factory 0ah eeprom id hardware 0bh subsystem id hardware 0ch subsystem vendor id hardware 0dh 0000b heartbeat packet pointer smb address field alert on lan* driver or hardware 0eh?2fh reserved 30h reserved for intel network interface division (nid) boot agent rom configuration (pxe and rpl version) firmware 31h reserved for intel nid boot agent rom configuration (pxe and rpl version) firmware 32h reserved for intel nid boot agent rom configuration (pxe and rpl version) firmware 33h?3ah reserved 3bh reserved for intel ? architecture labs (ial) boot rom configuration (pxe only) firmware 3ch?3fh reserved 40h?fah alert on lan alert packet structure alert on lan driver ffh checksum driver 82801BA ich2 and 82801BAm ich2-m datasheet 5-19 functional description 5.2.5 csma/cd unit the ich2 integrated lan controller csma/cd unit implements both the ieee 802.3 ethernet 10 mbps and ieee 802.3u fast ethernet 100 mbps standards. it also supports the 1 mbps home phoneline networking alliance (homepna*) specification effort. it performs all the csma/cd protocol functions such as transmission, reception, collision handling, etc. the lan controller csma/cd unit interfaces to the 82562et/em 10/100 mbps ethernet or the 82562eh 1 mbps homepna*-compliant lan connect component through the ich2?s lan connect interface signals. full duplex when operating in full duplex mode, the lan controller can transmit and receive frames simultaneously. transmission starts regardless of the state of the internal receive path. reception starts when the lan connect component detects a valid frame on its receive differential pair. when in full duplex mode, the ich2 integrated lan controller also supports the ieee 802.3x flow control standard. the lan controller operates in either half duplex mode or full duplex mode. for proper operation, both the lan controller csma/cd module and the discrete lan connect component must be set to the same duplex mode. the csma duplex mode is set by the lan controller configure command or forced by automatically tracking the mode in the lan connect component. following reset, the csma will default to automatically track the lan connect component duplex mode. the selection of duplex operation (full or half) and flow control is done in two levels: mac and lan connect. flow control the lan controller supports ieee 802.3x frame based flow control frames only in full duplex switched environments. the lan controller flow control feature is not intended to be used in shared media environments. flow control is optional in full duplex mode and is selected through software configuration. there are three modes of flow control that can be selected: frame-based transmit flow control, frame- based receive flow control, and none. address filtering modifications the lan controller can be configured to ignore one bit when checking for its individual address (ia) on incoming receive frames. the address bit, known as the upper/lower (u/l) bit, is the second least significant bit of the first byte of the ia. this bit may be used, in some cases, as a priority indication bit. when configured to do so, the lan controller passes any frame that matches all other 47 address bits of its ia, regardless of the u/l bit value. this configuration only affects the lan controller specific ia and not multicast, multi-ia or broadcast address filtering. the lan controller does not attribute any priority to frames with this bit set, it simply passes them to memory regardless of this bit. vlan support the lan controller supports the ieee 802.1 standard vlan. all vlan flows are implemented by software. the lan controller supports the reception of long frames; specifically frames longer than 1518 bytes, including the crc, if software sets the long receive ok bit in the configuration command. otherwise, ?long? frames are discarded. functional description 5-20 82801BA ich2 and 82801BAm ich2-m datasheet 5.2.6 media management interface the management interface allows the processor to control the lan connect component via a control register in the ich2 integrated lan controller. this allows the software driver to place the lan connect in specific modes such as full duplex, loopback, power down, etc., without the need for specific hardware pins to select the desired mode. this structure allows the lan controller to query the lan connect component for status of the link. this register is the mdi control register and resides at offset 10h in the lan controller csr. the mdi registers reside within the lan connect component, and are described in detail in the lan connect component?s datasheet. the processor writes commands to this register and the lan controller reads or writes the control/ status parameters to the lan connect component through the mdi register. 5.2.7 tco functionality the ich2-m integrated lan controller supports management communication to reduce total cost of ownership (tco). it has a system management bus (smb) on which the lan controller is a slave device. the smb is used as an interface between the lan controller and the integrated host controller. an eeprom of 256 words is required to support the heartbeat command. receive functionality in the power-up state, the lan controller transfers tco packets to the host as any other packet. these packets include a new status indication bit in the receive frame descriptor (rfd) status register and have a specific port number indicating tco packet recognition. in the power-down state, the tco packets are treated as wake-up packets. the ich2-m integrated lan controller asserts the pme# signal and delivers the first 120 bytes of the packet to the host. transmit functionality the ich2-m integrated lan controller supports the heartbeat (hb) transmission command from the smb interface. the send hb packet command includes a system health status issued by the integrated system controller. the lan controller computes a matched checksum and crc and transmits the hb packet from its serial eeprom. the hb packet size and structure are not limited as long as it fits within the eeprom size. in this case, the eeprom size is 256 words to enable the storage of the hb packet (the first 64 words are used for driver specific data). note: on the smb, the send heartbeat packet command is not normally used in the d0 power state. the one exception in which it is used in the d0 state is when the system is hung. in normal operating mode, the heartbeat packets are transmitted through the ich2-m integrated lan controller software similar to other packets. 5.3 lpc bridge (w/ system and management functions) (d31:f0) the lpc bridge function of the ich2 resides in pci device 31:function 0. in addition to the lpc bridge function, d31:f0 contains other functional units including dma, interrupt controllers, timers, power management, system management, gpio, and rtc. in this chapter, registers and functions associated with other functional units (power management, gpio, usb, ide, etc.) are described in their respective sections. 82801BA ich2 and 82801BAm ich2-m datasheet 5-21 functional description 5.3.1 lpc interface the ich2 implements an lpc interface as described in the lpc 1.0 specification. the lpc interface to the ich2 is shown in figure 5-6 . note that the ich2 implements all of the signals that are shown as optional, but peripherals are not required to do so. 5.3.1.1 lpc cycle types the ich2 implements all of the cycle types described in the lpc i/f 1.0 specification. table 5-3 shows the cycle types supported by the ich2. notes: 1. for memory cycles below 16 mb which do not target enabled fwh ranges, the ich2will perform standard lpc memory cycles. it will only attempt 8-bit transfers. if the cycle appears on pci as a 16-bit transfer, it will appear as two consecutive 8-bit transfers on lpc. likewise, if the cycle appears as a 32-bit transfer on pci, it will appear as four consecutive 8-bit transfers on lpc. if the cycle is not claimed by any peripheral, it will be subsequently aborted, and the ich2 will return a value of all 1s to the processor. this is done to maintain compatibility with isa memory cycles where pull-up resistors would keep the bus high if no device responds. 2. bus master read or write cycles must be naturally aligned. for example, a 1-byte transfer can be to any address. however, the 2-byte transfer must be word aligned (i.e. with an address where a0=0). a dword transfer must be dword aligned (i.e., with an address where a1and a0 are both 0) figure 5-6. lpc interface diagram ich super i/o pci bus pci clk pci rst# lad[3:0] pci serirq lpcpd# (optional) pci pme# lsmi# (optional) lframe# ldrq# (optional) gpi sus_stat# ich2 table 5-3. lpc cycle types supported cycle type comment memory read single: 1 byte only memory write single: 1 byte only i/o read 1 byte only. ich2 breaks up 16 and 32-bit processor cycles into multiple 8-bit transfers. see note 1 below. i/o write 1 byte only. ich2 breaks up 16 and 32-bit processor cycles into multiple 8-bit transfers. see note 1 below. dma read can be 1 or 2 bytes dma write can be 1 or 2 bytes bus master read can be 1, 2, or 4 bytes. (see note 2 below) bus master write can be 1, 2, or 4 bytes. (see note 2 below) functional description 5-22 82801BA ich2 and 82801BAm ich2-m datasheet 5.3.1.2 start field definition note: all other encodings are reserved. 5.3.1.3 cycle type / direction (cyctype + dir) the ich2 always drives bit 0 of this field to 0. peripherals running bus master cycles must also drive bit 0 to 0. table 5-5 shows the valid bit encodings. 5.3.1.4 size bits[3:2] are reserved. the ich2 always drives them to 00. peripherals running bus master cycles are also supposed to drive 00 for bits 3:2; however, the ich2 ignores those bits. table 5-6 shows the bit encodings for bits[1:0]. table 5-4. start field bit definitions bits[3:0] encoding definition 0000 start of cycle for a generic target. 0010 grant for bus master 0. 0011 grant for bus master 1. 1111 stop/abort: end of a cycle for a target. table 5-5. cycle type bit definitions bits[3:2] bit[1] definition 00 0 i/o read 00 1 i/o write 01 0 memory read 01 1 memory write 10 0 dma read 10 1 dma write 11 x reserved. if a peripheral performing a bus master cycle generates this value, the ich2 will abort the cycle. table 5-6. transfer size bit definition bits[1:0] size 00 8 bit transfer (1 byte) 01 16-bit transfer (2 bytes) 10 reserved. the ich2 never drives this combination. if a peripheral running a bus master cycle drives this combination, the ich2 may abort the transfer. 11 32 bit transfer (4 bytes) 82801BA ich2 and 82801BAm ich2-m datasheet 5-23 functional description 5.3.1.5 sync valid values for the sync field are listed in table 5-7 . note: all other combinations are reserved. 5.3.1.6 sync time-out there are several error cases that can occur on the lpc interface. table 5-8 indicates the failing case and the ich2 response. note: there may be other peripheral failure conditions; however, these are not handled by the ich2. 5.3.1.7 sync error indication the sync protocol allows the peripheral to report an error via the lad[3:0] = 1010b encoding. the intent of this encoding is to give peripherals a method of communicating errors to aid higher layers with more robust error recovery. if the ich2 was reading data from a peripheral, data will still be transferred in the next two nibbles. this data may be invalid; however, it must be transferred by the peripheral. if the ich2 was writing data to the peripheral, the data had already been transferred. in the case of multiple byte cycles (e.g., for memory and dma cycles) an error sync terminates the cycle. therefore, if the ich2 is transferring 4 bytes from a device and the device returns the error sync in the first byte, the other three bytes are not transferred. table 5-7. sync bit definition bits[3:0] indication 0000 ready: sync achieved with no error. for dma transfers, this also indicates dma request deassertion and no more transfers desired for that channel. 0101 short wait: part indicating wait states. for bus master cycles, the ich2 does not use this encoding. it will instead use the long wait encoding (see next encoding below). 0110 long wait: part indicating wait states; many wait states will be added. this encoding driven by the ich2 for bus master cycles, rather than the short wait (0101). 1001 ready more (used only by peripheral for dma cycle): sync achieved with no error and more dma transfers desired to continue after this transfer. this value is valid only on dma transfers and is not allowed for any other type of cycle. 1010 error: sync achieved with error. this is generally used to replace the serr# or iochk# signal on the pci/isa bus. it indicates that the data is to be transferred, but there is a serious error in this transfer. for dma transfers, this not only indicates an error, but also indicates dma request deassertion and no more transfers desired for that channel. table 5-8. ich2 response to sync failures possible sync failure ich2 response ich2 starts a memory, i/o, or dma cycle, but no device drives a valid sync after 4 consecutive clocks. this could occur if the processor tries to access an i/o location to which no device is mapped. ich2 aborts the cycle after the 4 th clock. ich2 drives a memory, i/o, or dma cycle, and a peripheral drives more than 8 consecutive valid sync patterns to insert wait states using the short (?0101b?) encoding for sync. this could occur if the peripheral is not operating properly. continues waiting ich2 starts a memory, i/o, or dma cycle, and a peripheral drives an invalid sync pattern. this could occur if the peripheral is not operating properly or if there is excessive noise on the lpc interface. ich2 aborts the cycle when the invalid sync is recognized. functional description 5-24 82801BA ich2 and 82801BAm ich2-m datasheet when recognizing the sync field indicating an error, the ich2 treats this the same as iochk# going active on the isa bus. 5.3.1.8 lframe# usage start of cycle for memory, i/o, and dma cycles, the ich2 asserts lframe# for 1 clock at the beginning of the cycle ( figure 5-7 ) during that clock, the ich2 drives lad[3:0] with the proper start field. abort mechanism when performing an abort, the ich2 drives lframe# active for 4 consecutive clocks. on the 4 th clock, the ich2 drives lad[3:0] to ?1111b?. the ich2 performs an abort for the following cases (possible failure cases): ? ich2 starts a memory, i/o, or dma cycle and no device drives a valid sync after 4 consecutive clocks. ? ich2 starts a memory, i/o, or dma cycle, and the peripheral drives an invalid sync pattern. ? a peripheral drives an illegal address when performing bus master cycles. ? a peripheral drives an invalid value. figure 5-7. typical timing for lframe# lframe# start lclk lad[3:0]# cyctype addr start dir & size tar sync data tar 1 - 8 clocks 2 clocks 1 - n clocks 2 clocks 2 clocks 1 clock 1 clock figure 5-8. abort mechanism lframe# start lclk lad[3:0]# cyctype addr dir & size tar sync peripheral must stop driving too many syncs causes timeout chipset will drive high 82801BA ich2 and 82801BAm ich2-m datasheet 5-25 functional description 5.3.1.9 i/o cycles for i/o cycles targeting registers specified in the ich2?s decode ranges, the ich2 performs i/o cycles as defined in the lpc specification. these are 8-bit transfers. if the processor attempts a 16-bit or 32-bit transfer, the ich2 will break the cycle up into multiple 8-bit transfers to consecutive i/o addresses. note: if the cycle is not claimed by any peripheral (and subsequently aborted), the ich2 returns all 1s (ffh) to the processor. this is to maintain compatibility with isa i/o cycles where pull-up resistors would keep the bus high if no device responds. 5.3.1.10 bus master cycles the ich2 supports bus master cycles and requests (using ldrq#) as defined in the lpc specification. the ich2 has two ldrq# inputs; thus, ich2 supports two separate bus master devices. it uses the associated start fields for bus master 0 (?0010b?) or bus master 1 (?0011b?). note: the ich2 does not support lpc bus masters performing i/o cycles. lpc bus masters should only perform memory read or memory write cycles. 5.3.1.11 lpc power management lpcpd# protocol same timings as for sus_stat#. upon driving sus_stat# low, lpc peripherals will drive ldrq# low or tri-state it. ich2 shuts off the ldrq# input buffers. after driving sus_stat# active, the ich2 drives lframe# low and tri-states (or drive low) lad[3:0]. clkrun# protocol (82801BAm ich2-m only) 5.3.1.12 configuration and ich2 implications lpc interface decoders to allow the i/o cycles and memory mapped cycles to go to the lpc i/f, the ich2 includes several decoders. during configuration, the ich2 must be programmed with the same decode ranges as the peripheral. the decoders are programmed via the device 31:function 0 configuration space. note: the ich2 can not accept pci write cycles from pci-to-pci bridges or devices with similar characteristics (specifically those with a ?retry read? feature which is enabled) to an lpc device if there is an outstanding lpc read cycle towards the same pci device or bridge. these cycles are not part of normal system operation; however, they may be encountered as part of platform validation testing using custom test fixtures. bus master device mapping and start fields bus masters must have a unique start field. in the case of the ich2, which supports 2 lpc bus masters, it will drive 0010 for the start field for grants to bus master #0 (requested via ldrq[0]#) and 0011 for grants to bus master #1 (requested via ldrq[1]#.). thus, no registers are needed to configure the start fields for a particular bus master. for the ich2-m, the clkrun# protocol is the same as the pci specification. stopping the pci clock stops the lpc clock. functional description 5-26 82801BA ich2 and 82801BAm ich2-m datasheet 5.4 dma operation (d31:f0) the ich2 supports two types of dma: lpc and pc/pci. dma via lpc is similar to isa dma. lpc dma and pc/pci dma use the ich2?s dma controller. the dma controller has registers that are fixed in the lower 64 kb of i/o space. the dma controller is configured using registers in the pci configuration space. these registers allow configuration of individual channels for use by lpc or pc/pci dma. the dma circuitry incorporates the functionality of two 82c37 dma controllers with seven independently programmable channels ( figure 5-9 ). dma controller 1 (dma-1) corresponds to dma channels 0?3 and dma controller 2 (dma-2) corresponds to channels 5?7. dma channel 4 is used to cascade the two controllers and will default to cascade mode in the dma channel mode (dcm) register. channel 4 is not available for any other purpose. in addition to accepting requests from dma slaves, the dma controller also responds to requests that software initiates. software may initiate a dma service request by setting any bit in the dma channel request register to a 1. each dma channel is hardwired to the compatible settings for dma device size: channels 3?0 are hardwired to 8-bit, count-by-bytes transfers and channels 7?5 are hardwired to 16-bit, count-by- words (address shifted) transfers. ich2 provides 24-bit addressing in compliance with the isa-compatible specification. each channel includes a 16-bit isa-compatible current register which holds the 16 least-significant bits of the 24-bit address, an isa-compatible page register which contains the eight next most significant bits of address. the dma controller also features refresh address generation and autoinitialization following a dma termination. 5.4.1 channel priority for priority resolution, the dma consists of two logical channel groups: channels 0?3 and channels 4?7. each group may be in either fixed or rotate mode, as determined by the dma command register. dma i/o slaves normally assert their dreq line to arbitrate for dma service. however, a software request for dma service can be presented through each channel's dma request register. a software request is subject to the same prioritization as any hardware request. see the detailed register description for request register programming information in the dma register description section. figure 5-9. ich2 dma controller channel 0 channel 1 channel 2 channel 3 channel 4 channel 5 channel 6 channel 7 dma-1 dma-2 82801BA ich2 and 82801BAm ich2-m datasheet 5-27 functional description fixed priority the initial fixed priority structure is as follows: the fixed priority ordering is 0, 1, 2, 3, 5, 6, and 7. in this scheme, channel 0 has the highest priority and channel 7 has the lowest priority. channels 3?0 of dma-1 assume the priority position of channel 4 in dma-2, thus taking priority over channels 5, 6, and 7. rotating priority rotation allows for "fairness" in priority resolution. the priority chain rotates so that the last channel serviced is assigned the lowest priority in the channel group (0?3, 5?7). channels 0?3 rotate as a group of 4. they are always placed between channel 5 and channel 7 in the priority list. channel 5?7 rotate as part of a group of 4. that is, channels (5?7) form the first three positions in the rotation while channel group (0?3) form the fourth position in the arbitration. 5.4.2 address compatibility mode when the dma is operating, the addresses do not increment or decrement through the high and low page registers. therefore, if a 24-bit address is 01ffffh and increments, the next address will be 010000h, not 020000h. similarly, if a 24-bit address is 020000h and decrements, the next address will be 02ffffh, not 01ffffh. this is compatible with the 82c37 and page register implementation used in the pc-at. this mode is set after cpurst is valid. 5.4.3 summary of dma transfer sizes table 5-9 lists each of the dma device transfer sizes. the column labeled "current byte/word count register" indicates that the register contents represents either the number of bytes to transfer or the number of 16-bit words to transfer. the column labeled "current address increment/ decrement" indicates the number added to or taken from the current address register after each dma transfer cycle. the dma channel mode register determines if the current address register is incremented or decremented. high priority.....low priority (0, 1, 2, 3) (5, 6, 7) functional description 5-28 82801BA ich2 and 82801BAm ich2-m datasheet address shifting when programmed for 16-bit i/o count by words the ich2 maintains compatibility with the implementation of the dma in the pc-at that used the 82c37. the dma shifts the addresses for transfers to/from a 16-bit device count-by-words. note that the least significant bit of the low page register is dropped in 16-bit shifted mode. when programming the current address register (when the dma channel is in this mode), the current address must be programmed to an even address with the address value shifted right by one bit. the address shifting is shown in table 5-10 . note: note: the least significant bit of the page register is dropped in 16-bit shifted mode. 5.4.4 autoinitialize by programming a bit in the dma channel mode register, a channel may be set up as an autoinitialize channel. when a channel undergoes autoinitialization, the original values of the current page, current address and current byte/word count registers are automatically restored from the base page, address, and byte/word count registers of that channel following tc. the base registers are loaded simultaneously with the current registers by the processor when the dma channel is programmed and remain unchanged throughout the dma service. the mask bit is not set when the channel is in autoinitialize. following autoinitialize, the channel is ready to perform another dma service, without processor intervention, as soon as a valid dreq is detected. table 5-9. dma transfer size dma device date size and word count current byte/word count register current address increment/decrement 8-bit i/o, count by bytes bytes 1 16-bit i/o, count by words (address shifted) words 1 table 5-10. address shifting in 16-bit i/o dma transfers output address 8-bit i/o programmed address (ch 0?3) 16-bit i/o programmed address (ch 5?7) (shifted) a0 a[16:1] a[23:17] a0 a[16:1] a[23:17] 0 a[15:0] a[23:17] 82801BA ich2 and 82801BAm ich2-m datasheet 5-29 functional description 5.4.5 software commands there are three additional special software commands that the dma controller can execute. the three software commands are: ? clear byte pointer flip-flop ? master clear ? clear mask register they do not depend on any specific bit pattern on the data bus. clear byte pointer flip-flop this command is executed prior to writing or reading new address or word count information to/from the dma controller. this initializes the flip-flop to a known state so that subsequent accesses to register contents by the processor addresses upper and lower bytes in the correct sequence. when the host processor is reading or writing dma registers, two byte pointer flip-flops are used; one for channels 0?3 and one for channels 4?7. both of these act independently. there are separate software commands for clearing each of them (0ch for channels 0?3, 0d8h for channels 4?7). dma master clear this software instruction has the same effect as the hardware reset. the command, status, request, and internal first/last flip-flop registers are cleared and the mask register is set. the dma controller enters the idle cycle. there are two independent master clear commands; 0dh acts on channels 0?3, and 0dah acts on channels 4?7. clear mask register this command clears the mask bits of all four channels, enabling them to accept dma requests. i/o port 00eh is used for channels 0?3 and i/o port 0dch is used for channels 4?7. functional description 5-30 82801BA ich2 and 82801BAm ich2-m datasheet 5.5 pci dma the ich2 provides support for the pc/pci dma protocol. pc/pci dma uses dedicated request and grant signals to permit pci devices to request transfers associated with specific dma channels. upon receiving a request and getting control of the pci bus, the ich2 performs a two- cycle transfer. for example, if data is to be moved from the peripheral to main memory, the ich2 first reads data from the peripheral and then writes the data to main memory. the location in main memory is the current address registers in the 8237. ich2 supports up to 2 pc/pci req/gnt pairs, req[a:b]# and gnt[a:b]#. a 16-bit register is included in the ich2 function 0 pci configuration space at offset 90h. it is divided into seven 2-bit fields that are used to configure the 7 dma channels. each dma channel can be configured to one of two options: ? lpc dma ? pc/pci style dma using the req/gnt signals it is not possible for a particular dma channel to be configured for more than one style of dma; however, the seven channels can be programmed independently. for example, channel 3 can be set up for pc/pci and channel 5 set up for lpc dma. the ich2 req[a:b]# and gnt[a:b]# can be configured for support of a pc/pci dma expansion agent. the pci dma expansion agent can then provide dma service or isa bus master service using the ich2 dma controller. the req#/gnt# pair must follow the pc/pci serial protocol described in the following section. 5.5.1 pci dma expansion protocol the pci expansion agent must support the pci expansion channel passing protocol defined in figure 5-10 for both the req# and gnt# pins. the requesting device must encode the channel request information as shown above, where ch0?ch7 are one clock active high states representing dma channel requests 0?7. the ich2 encodes the granted channel on the gnt# line as shown above where the bits have the same meaning as shown in figure 5-10 . for example, the sequence [start, bit 0, bit 1, bit 2]=[0,1,0,0] grants dma channel 1 to the requesting device, and the sequence [start, bit 0, bit 1, bit 2]=[0,0,1,1] grants dma channel 6 to the requesting device. figure 5-10. dma serial channel passing protocol pciclk start ch0 ch1 ch2 ch3 ch4 ch5 ch6 ch7 bit0 bit1 bit2 start req# gnt# 82801BA ich2 and 82801BAm ich2-m datasheet 5-31 functional description all pci dma expansion agents must use the channel passing protocol described above. they must also work as follows: 1. if a pci dma expansion agent has more than one request active, it must resend the request serial protocol after one of the requests has been granted the bus and it has completed its transfer. the expansion device should drive its req# inactive for two clocks and then transmit the serial channel passing protocol again, even if there are no new requests from the pci expansion agent to ich2. for example, if a pci expansion agent had active requests for dma channel 1 and channel 5, it would pass this information to the ich2 through the expansion channel passing protocol. if, after receiving gnt# (assume for ch5) and having the device finish its transfer (device stops driving request to pci expansion agent), it would then need to re-transmit the expansion channel passing protocol to inform the ich2 that dma channel 1 was still requesting the bus, even if that was the only request the expansion device had pending. 2. if a pci dma expansion agent has a request go inactive before ich2 asserts gnt#, it must resend the expansion channel passing protocol to update the ich2 with this new request information. for example, if a pci expansion agent has dma channel 1 and 2 requests pending, it sends them serially to ich2 using the expansion channel passing protocol. if, however, dma channel 1 goes inactive into the expansion agent before the expansion agent receives a gnt# from ich2, the expansion agent must pull its req# line high for 1clock and resend the expansion channel passing information with only dma channel 2 active. note that the ich2 does not do anything special to catch this case because a dreq going inactive before a dack# is received is not allowed in the isa dma protocol and, therefore, does not need to work properly in this protocol either. this requirement is needed to be able to support plug-n-play isa devices that toggle dreq# lines to determine if those lines are free in the system. 3. if a pci expansion agent has sent its serial request information and receives a new dma request before receiving gnt#, the agent must resend the serial request with the new request active. for example, if a pci expansion agent has already passed requests for dma channel 1 and 2 and detects dreq 3 active before a gnt is received, the device must pull its req# line high for one clock and resend the expansion channel passing information with all three channels active. the three cases above require the following functionality in the pci dma expansion device: ? drive req# inactive for one clock to signal new request information. ? drive req# inactive for two clocks to signal that a request that had been granted the bus has gone inactive. ? the req# and gnt# state machines must run independently and concurrently (i.e., a gnt# could be received while in the middle of sending a serial req# or a gnt# could be active while req# is inactive). functional description 5-32 82801BA ich2 and 82801BAm ich2-m datasheet 5.5.2 pci dma expansion cycles ich2?s support of the pc/pci dma protocol currently consists of four types of cycles: memory- to-i/o, i/o-to-memory, verify, and isa master cycles. isa masters are supported through the use of a dma channel that has been programmed for cascade mode. the dma controller does a two cycle transfer (a load followed by a store) as opposed to the isa "fly-by" cycle for pc/pci dma agents. the memory portion of the cycle generates a pci memory read or memory write bus cycle, its address representing the selected memory. the i/o portion of the dma cycle generates a pci i/o cycle to one of four i/o addresses ( table 5-11 ). note that these cycles must be qualified by an active gnt# signal to the requesting device. 5.5.3 dma addresses the memory portion of the cycle generates a pci memory read or memory write bus cycle; its address representing the selected memory. the i/o portion of the dma cycle generates a pci i/o cycle to one of the four i/o addresses listed in table 5-11 . 5.5.4 dma data generation the data generated by pc/pci devices on i/o reads when they have an active gnt# is on the lower two bytes of the pci ad bus. table 5-12 lists the pci pins that the data appears for 8 and 16 bit channels. each i/o read results in one memory write and each memory read results in one i/o write. if the i/o device is 8 bit, the ich2 performs an 8 bit memory write. the ich2 does not assemble the i/o read into a dword for writing to memory. similarly, the ich2 does not disassemble a dword read from memory to the i/o device. table 5-11. dma cycle vs. i/o address dma cycle type dma i/o address pci cycle type normal 00h i/o read/write normal tc 04h i/o read/write verify 0c0h i/o read verify tc 0c4h i/o read table 5-12. pci data bus vs. dma i/o port size pci dma i/o port size pci data bus connection byte ad[7:0] word ad[15:0] 82801BA ich2 and 82801BAm ich2-m datasheet 5-33 functional description 5.5.5 dma byte enable generation the byte enables generated by the ich2 on i/o reads and writes must correspond to the size of the i/o device. table 5-13 defines the byte enables asserted for 8 and 16 bit dma cycles. note: for verify cycles, the value of the byte enables (bes) are a ?don?t care?. 5.5.6 dma cycle termination dma cycles are terminated when a terminal count is reached in the dma controller and the channel is not in autoinitialize mode or when the pc/pci device deasserts its request. the pc/pci device must follow explicit rules when deasserting its request or the ich2 may not see it in time and run an extra i/o and memory cycle. the pc/pci device must deassert its request 7 pciclks before it generates trdy# on the i/o read or write cycle or the ich2 is allowed to generate another dma cycle. for transfers to memory, this means that the memory portion of the cycle will be run without an asserted pc/pci req#. 5.5.7 lpc dma dma on lpc is handled through the use of the ldrq# lines from peripherals and special encodings on lad[3:0] from the host. single, demand, verify, and increment modes are supported on the lpc interface. channels 0?3 are 8 bit channels. channels 5?7 are 16 bit channels. channel 4 is reserved as a generic bus master request. 5.5.8 asserting dma requests peripherals that need dma service encode their requested channel number on the ldrq# signal. to simplify the protocol, each peripheral on the lpc i/f has its own dedicated ldrq# signal (they may not be shared between two separate peripherals). the ich2 has two ldrq# inputs, allowing at least two devices to support dma or bus mastering. ldrq# is synchronous with lclk (pci clock). as shown in figure 5-11 the peripheral uses the following serial encoding sequence: ? peripheral starts the sequence by asserting ldrq# low (start bit). ldrq# is high during idle conditions. ? the next 3 bits contain the encoded dma channel number (msb first). ? the next bit (act) indicates whether the request for the indicated dma channel is active or inactive. the act bit will be a 1 (high) to indicate if it is active and 0 (low) if it is inactive. the case where act is low will be rare, and is only used to indicate that a previous request for that channel is being abandoned. ? after the active/inactive indication, the ldrq# signal must go high for at least 1 clock. after that one clock, ldrq# signal can be brought low to the next encoding sequence. table 5-13. dma i/o cycle width vs. be[3:0]# be[3:0]# description 1110b 8-bit dma i/o cycle: channels 0-3 1100b 16-bit dma i/o cycle: channels 5-7 functional description 5-34 82801BA ich2 and 82801BAm ich2-m datasheet if another dma channel also needs to request a transfer, another sequence can be sent on ldrq#. for example, if an encoded request is sent for channel 2 and then channel 3 needs a transfer before the cycle for channel 2 is run on the interface, the peripheral can send the encoded request for channel 3. this allows multiple dma agents behind an i/o device to request use of the lpc interface and the i/o device does not need to self-arbitrate before sending the message. 5.5.9 abandoning dma requests dma requests can be deasserted in two fashions: on error conditions by sending an ldrq# message with the ?act? bit set to 0, or normally through a sync field during the dma transfer. this section describes boundary conditions where the dma request needs to be removed prior to a data transfer. there may be some special cases where the peripheral desires to abandon a dma transfer. the most likely case of this occurring is due to a floppy disk controller that has overrun or underrun its fifo, or software stopping a device prematurely. in these cases, the peripheral wishes to stop further dma activity. it may do so by sending an ldrq# message with the act bit as 0. however, since the dma request was seen by the ich2, there is no guarantee that the cycle has not been granted and will shortly run on lpc. therefore, peripherals must take into account that a dma cycle may still occur. the peripheral can choose not to respond to this cycle, in which case the host aborts it or the host can choose to complete the cycle normally with any random data. this method of dma deassertion should be prevented when possible to limit boundary conditions both on the ich2 and the peripheral. figure 5-11. dma request assertion through ldrq# start msb lsb act start lclk ldrq# 82801BA ich2 and 82801BAm ich2-m datasheet 5-35 functional description 5.5.10 general flow of dma transfers arbitration for dma channels is performed through the 8237 within the host. once the host has won arbitration on behalf of a dma channel assigned to lpc, it asserts lframe# on the lpc i/f and begins the dma transfer. the general flow for a basic dma transfer is as follows: 1. ich2 starts transfer by asserting 0000b on lad[3:0] with lframe# asserted. 2. ich2 asserts ?cycle type? of dma, direction based on dma transfer direction. 3. ich2 asserts channel number and, if applicable, terminal count. 4. ich2 indicates the size of the transfer: 8 or 16 bits. 5. if a dma read, ? the ich2 drives the first 8 bits of data and turns the bus around. ? the peripheral acknowledges the data with a valid sync. ? if a 16 bit transfer, the process is repeated for the next 8 bits. 6. if a dma write, ? the ich2 turns the bus around and waits for data. ? the peripheral indicates data ready through sync and transfers the first byte. ? if a 16 bit transfer, the peripheral indicates data ready and transfers the next byte. 7. the peripheral turns around the bus. 5.5.11 terminal count terminal count is communicated through lad[3] on the same clock that dma channel is communicated on lad[2:0]. this field is the channel field. terminal count indicates the last byte of transfer, based upon the size of the transfer. for example, on an 8-bit transfer size (size field is 00b), if the tc bit is set, this is the last byte. on a 16-bit transfer (size field is 01b), if the tc bit is set, the second byte is the last byte. therefore, the peripheral must internalize the tc bit when the channel field is communicated and only signal tc when the last byte of that transfer size has been transferred. 5.5.12 verify mode verify mode is supported on the lpc interface. a verify transfer to the peripheral is similar to a dma write where the peripheral is transferring data to main memory. the indication from the host is the same as a dma write, so the peripheral will be driving data onto the lpc interface. however, the host does not transfer this data into main memory. functional description 5-36 82801BA ich2 and 82801BAm ich2-m datasheet 5.5.13 dma request deassertion an end of transfer is communicated to the ich2 through a special sync field transmitted by the peripheral. an lpc device must not attempt to signal the end of a transfer by deasserting ldreq#. if a dma transfer is several bytes (e.g., a transfer from a demand mode device), the ich2 needs to know when to deassert the dma request based on the data currently being transferred. the dma agent uses a sync encoding on each byte of data being transferred which indicates to the ich2 whether this is the last byte of transfer or if more bytes are requested. to indicate the last byte of transfer, the peripheral uses a sync value of 0000b (ready with no error), or ?1010b? (ready with error). these encodings tell the ich2 that this is the last piece of data transferred on a dma read (ich2 to peripheral), or the byte which follows is the last piece of data transferred on a dma write (peripheral to ich2). when the ich2 sees one of these two encodings, it ends the dma transfer after this byte and deasserts the dma request to the 8237. therefore, if the ich2 indicated a 16 bit transfer, the peripheral can end the transfer after one byte by indicating a sync value of 0000b or 1010b. the ich2 will not attempt to transfer the second byte, and will deassert the dma request internally. if the peripheral indicates a 0000b or 1010b sync pattern on the last byte of the indicated size, then the ich2 will only deassert the dma request to the 8237 since it does not need to end the transfer. if the peripheral wishes to keep the dma request active, it uses a sync value of 1001b (ready plus more data). this indicates to the 8237 that more data bytes are requested after the current byte has been transferred; the ich2 keeps the dma request active to the 8237. therefore, on an 8-bit transfer size, if the peripheral indicates a sync value of 1001b to the ich2, the data will be transferred and the dma request remains active to the 8237. at a later time, the ich2 will then come back with another start - cyctype - channel - size etc. combination to initiate another transfer to the peripheral. the peripheral must not assume that the next start indication from the ich2 is another grant to the peripheral if it had indicated a sync value of 1001b. on a single mode dma device, the 8237 re-arbitrates after every transfer. only demand mode dma devices can be guaranteed that they will receive the next start indication from the ich2. note: indicating a 0000b or ?1010b? encoding on the sync field of an odd byte of a 16 bit channel (first byte of a 16 bit transfer) is an error condition. note: the host stops the transfer on the lpc bus as indicated, fill the upper byte with random data on dma writes (peripheral to memory), and indicates to the 8237 that the dma transfer occurred, incrementing the 8237?s address and decrementing its byte count. 82801BA ich2 and 82801BAm ich2-m datasheet 5-37 functional description 5.5.14 sync field / ldrq# rules since dma transfers on lpc are requested through an ldrq# assertion message and are ended through a sync field during the dma transfer, the peripheral must obey the following rule when initiating back-to-back transfers from a dma channel. the peripheral must not assert another message for 8 lclks after a deassertion is indicated through the sync field. this is needed to allow the 8237, which typically runs off a much slower internal clock, to see a message deasserted before it is re-asserted so that it can arbitrate to the next agent. under default operation, the host will only perform 8-bit transfers on 8-bit channels and 16-bit transfers on 16-bit channels. the method by which this communication between host and peripheral through system bios is performed is beyond the scope of this specification. since the lpc host and lpc peripheral are motherboard devices, no ?plug-n-play? registry is required. the peripheral must not assume that the host will be able to perform transfer sizes that are larger than the size allowed for the dma channel and be willing to accept a size field that is smaller than what it may currently have buffered. to that end, it is recommended that future devices which may appear on the lpc bus, which require higher bandwidth than 8 bit or 16 bit dma allow, do so with a bus mastering interface and not rely on the 8237. functional description 5-38 82801BA ich2 and 82801BAm ich2-m datasheet 5.6 8254 timers (d31:f0) the ich2 contains three counters that have fixed uses. all registers and functions associated with the 8254 timers are in the core well. the 8254 unit is clocked by a 14.31818 mhz clock. counter 0, system timer this counter functions as the system timer by controlling the state of irq0 and is typically programmed for mode 3 operation. the counter produces a square wave with a period equal to the product of the counter period (838 ns) and the initial count value. the counter loads the initial count value one counter period after software writes the count value to the counter i/o address. the counter initially asserts irq0 and decrements the count value by two each counter period. the counter negates irq0 when the count value reaches 0. it then reloads the initial count value and again decrements the initial count value by two each counter period. the counter then asserts irq0 when the count value reaches 0, reloads the initial count value, and repeats the cycle; alternately asserting and negating irq0. counter 1, refresh request signal this counter provides the refresh request signal and is typically programmed for mode 2 operation. the counter negates refresh request for one counter period (838 ns) during each count cycle. the initial count value is loaded one counter period after being written to the counter i/o address. the counter initially asserts refresh request and negates it for 1 counter period when the count value reaches 1. the counter then asserts refresh request and continues counting from the initial count value. counter 2, speaker tone this counter provides the speaker tone and is typically programmed for mode 3 operation. the counter provides a speaker frequency equal to the counter clock frequency (1.193 mhz) divided by the initial count value. the speaker must be enabled by a write to port 061h (see nmi status and control ports). 5.6.1 timer programming the counter/timers are programmed in the following fashion: 1. write a control word to select a counter 2. write an initial count for that counter. 3. load the least and/or most significant bytes (as required by control word bits 5, 4) of the 16-bit counter. 4. repeat with other counters only two conventions need to be observed when programming the counters. first, for each counter, the control word must be written before the initial count is written. second, the initial count must follow the count format specified in the control word (least significant byte only, most significant byte only, or least significant byte and then most significant byte). a new initial count may be written to a counter at any time without affecting the counter's programmed mode. counting is affected as described in the mode definitions. the new count must follow the programmed count format. caution: if a counter is programmed to read/write two-byte counts, the following applies: a program must not transfer control between writing the first and second byte to another routine which also writes into that same counter. otherwise, the counter will be loaded with an incorrect count. 82801BA ich2 and 82801BAm ich2-m datasheet 5-39 functional description the control word register at port 43h controls the operation of all three counters. several commands are available: ? control word command. specifies which counter to read or write, the operating mode, and the count format (binary or bcd). ? counter latch command. latches the current count so that it can be read by the system. the countdown process continues. ? read back command. reads the count value, programmed mode, the current state of the out pins, and the state of the null count flag of the selected counter. table 5-14 lists the six operating modes for the interval counters. 5.6.2 reading from the interval timer it is often desirable to read the value of a counter without disturbing the count in progress. there are three methods for reading the counters: a simple read operation, counter latch command, and the read-back command. each is explained below. with the simple read and counter latch command methods, the count must be read according to the programmed format; specifically, if the counter is programmed for two byte counts, two bytes must be read. the two bytes do not have to be read one right after the other. read, write, or programming operations for other counters may be inserted between them. simple read the first method is to perform a simple read operation. the counter is selected through port 40h (counter 0), 41h (counter 1), or 42h (counter 2). note: performing a direct read from the counter will not return a determinate value because the counting process is asynchronous to read operations. however, in the case of counter 2, the count can be stopped by writing to the gate bit in port 61h. table 5-14. counter operating modes mode function description 0 out signal on end of count (=0) output is 0?. when count goes to 0, output goes to 1? and stays at 1? until counter is reprogrammed. 1 hardware retriggerable one-shot output is 0?. when count goes to 0, output goes to 1? for one clock time. 2 rate generator (divide by n counter) output is 1?. output goes to 0? for one clock time, then back to 1? and counter is reloaded. 3 square wave output output is 1?. output goes to 0? when counter rolls over, and counter is reloaded. output goes to 1? when counter rolls over, and counter is reloaded, etc. 4 software triggered strobe output is 1?. output goes to 0? when count expires for one clock time. 5 hardware triggered strobe output is 1?. output goes to 0? when count expires for one clock time. functional description 5-40 82801BA ich2 and 82801BAm ich2-m datasheet counter latch command the counter latch command, written to port 43h, latches the count of a specific counter at the time the command is received. this command is used to ensure that the count read from the counter is accurate, particularly when reading a two-byte count. the count value is then read from each counter's count register as was programmed by the control register. the count is held in the latch until it is read or the counter is reprogrammed. the count is then unlatched. this allows reading the contents of the counters on the fly without affecting counting in progress. multiple counter latch commands may be used to latch more than one counter. counter latch commands do not affect the programmed mode of the counter. if a counter is latched and then, some time later, latched again before the count is read, the second counter latch command is ignored. the count read will be the count at the time the first counter latch command was issued. read back command the read back command, written to port 43h, latches the count value, programmed mode, and current states of the out pin and null count flag of the selected counter or counters. the value of the counter and its status may then be read by i/o access to the counter address. the read back command may be used to latch multiple counter outputs at one time. this single command is functionally equivalent to several counter latch commands, one for each counter latched. each counter's latched count is held until it is read or reprogrammed. once read, a counter is unlatched. the other counters remain latched until they are read. if multiple count read back commands are issued to the same counter without reading the count, all but the first are ignored. the read back command may additionally be used to latch status information of selected counters. the status of a counter is accessed by a read from that counter's i/o port address. if multiple counter status latch operations are performed without reading the status, all but the first are ignored. both count and status of the selected counters may be latched simultaneously. this is functionally the same as issuing two consecutive, separate read back commands. if multiple count and/or status read back commands are issued to the same counters without any intervening reads, all but the first are ignored. if both count and status of a counter are latched, the first read operation from that counter will return the latched status, regardless of which was latched first. the next one or two reads, depending on whether the counter is programmed for one or two type counts, return the latched count. subsequent reads return unlatched count. 82801BA ich2 and 82801BAm ich2-m datasheet 5-41 functional description 5.7 8259 interrupt controllers (pic) (d31:f0) the ich2 incorporates the functionality of two 8259 interrupt controllers that provide system interrupts for the isa compatible interrupts. these interrupts are: system timer, keyboard controller, serial ports, parallel ports, floppy disk, ide, mouse, and dma channels. in addition, this interrupt controller can support the pci-based interrupts, by mapping the pci interrupt onto the compatible isa interrupt line. each 8259 core supports 8 interrupts, numbered 0?7. table 5-15 shows how the cores are connected. . the ich2 cascades the slave controller onto the master controller through master controller interrupt input 2. this means there are only 15 possible interrupts for the ich2 pic. interrupts can individually be programmed to be edge or level, except for irq[0, 2, 8#, 13]. note that previous piixn devices internally latched irq[12 and 1] and required a port 60h read to clear the latch. the ich2 can be programmed to latch irq[12 or 1] (see bit 11 and bit 12 in general control register, d31:f0, offset d0h). table 5-15. interrupt controller core connections 8259 8259 input typical interrupt source connected pin / function master 0 internal internal timer / counter 0 output 1 keyboard irq1 via serirq 2 internal slave controller intr output 3 serial port a irq3 via serirq 4 serial port b irq4 via serirq 5 parallel port / generic irq5 via serirq 6 floppy disk irq6 via serirq 7 parallel port / generic irq7 via serirq slave 0 internal real time clock internal rtc 1 generic irq9 via serirq 2 generic irq10 via serirq 3 generic irq11 via serirq 4 ps/2 mouse irq12 via serirq 5 internal state machine output based on processor ferr# assertion. 6 primary ide cable irq14 from input signal or via serirq 7 secondary ide cable irq15 from input signal or via serirq functional description 5-42 82801BA ich2 and 82801BAm ich2-m datasheet 5.7.1 interrupt handling 5.7.1.1 generating interrupts the pic interrupt sequence involves three bits, from the irr, isr, and imr for each interrupt level. these bits are used to determine the interrupt vector returned, and status of any other pending interrupts. table 5-16 defines the irr, isr, and imr. 5.7.1.2 acknowledging interrupts the processor generates an interrupt acknowledge cycle that is translated by the host bridge into a pci interrupt acknowledge cycle to the ich2. the pic translates this command into two internal inta# pulses expected by the 8259 cores. the pic uses the first internal inta# pulse to freeze the state of the interrupts for priority resolution. on the second inta# pulse, the master or slave sends the interrupt vector to the processor with the acknowledged interrupt code. this code is based on bits [7:3] of the corresponding icw2 register combined with three bits representing the interrupt within that controller. table 5-16. interrupt status registers bit description irr interrupt request register. this bit is set on a low-to-high transition of the interrupt line in edge mode and by an active high level in level mode. this bit is set whether or not the interrupt is masked. however, a masked interrupt will not generate intr. isr interrupt service register. this bit is set, and the corresponding irr bit cleared, when an interrupt acknowledge cycle is seen and the vector returned is for that interrupt. imr interrupt mask register. this bit determines whether an interrupt is masked. masked interrupts will not generate intr. table 5-17. content of interrupt vector byte master,slave interrupt bits [7:3] bits [2:0] irq[7,15] icw2[7:3] 111 irq[6,14] 110 irq[5,13] 101 irq[4,12] 100 irq[3,11] 011 irq[2,10] 010 irq[1,9] 001 irq[0,8] 000 82801BA ich2 and 82801BAm ich2-m datasheet 5-43 functional description 5.7.1.3 hardware/software interrupt sequence 1. one or more of the interrupt request lines (irq) are raised high in edge mode, or seen high in level mode, setting the corresponding irr bit. 2. the pic sends intr active to the processor if an asserted interrupt is not masked. 3. the processor acknowledges the intr and responds with an interrupt acknowledge cycle. the cycle is translated into a pci interrupt acknowledge cycle by the host bridge. this command is broadcast over pci by the ich2. 4. upon observing its own interrupt acknowledge cycle on pci, the ich2 converts it into the two cycles that the internal 8259 pair can respond. each cycle appears as an interrupt acknowledge pulse on the internal inta# pin of the cascaded interrupt controllers. 5. upon receiving the first internally generated inta# pulse, the highest priority isr bit is set and the corresponding irr bit is reset. on the trailing edge of the first pulse a slave identification code is broadcast by the master to the slave on a private, internal three bit wide bus. the slave controller uses these bits to determine if it must respond with an interrupt vector during the second inta# pulse. 6. upon receiving the second internally generated inta# pulse, the pic returns the interrupt vector. if no interrupt request is present because the request was too short in duration, the pic will return vector 7 from the master controller. 7. this completes the interrupt cycle. in aeoi mode the isr bit is reset at the end of the second inta# pulse. otherwise, the isr bit remains set until an appropriate eoi command is issued at the end of the interrupt subroutine. 5.7.2 initialization command words (icwx) before the operation can begin, each 8259 must be initialized. in the ich2 this is a four-byte sequence. the four initialization command words are referred to by their acronyms: icw1, icw2, icw3, and icw4. the base address for each 8259 initialization command word is a fixed location in the i/o memory space: 20h for the master controller and a0h for the slave controller. icw1 an i/o write to the master or slave controller base address with data bit 4 equal to 1 is interpreted as a write to icw1. upon sensing this write, the ich2 pic expects three more byte writes to 21h for the master controller, or a1h for the slave controller, to complete the icw sequence. a write to icw1 starts the initialization sequence during which the following automatically occur: 1. following initialization, an interrupt request (irq) input must make a low-to-high transition to generate an interrupt. 2. the interrupt mask register is cleared. 3. irq7 input is assigned priority 7. 4. the slave mode address is set to 7. 5. special mask mode is cleared and status read is set to irr. functional description 5-44 82801BA ich2 and 82801BAm ich2-m datasheet icw2 the second write in the sequence (icw2) is programmed to provide bits 7:3 of the interrupt vector that will be released during an interrupt acknowledge. a different base is selected for each interrupt controller. icw3 the third write in the sequence (icw3) has a different meaning for each controller. ? for the master controller, icw3 is used to indicate which irq input line is used to cascade the slave controller. within the ich2, irq2 is used. therefore, bit 2 of icw3 on the master controller is set to a 1 and the other bits are set to 0s. ? for the slave controller, icw3 is the slave identification code used during an interrupt acknowledge cycle. on interrupt acknowledge cycles, the master controller broadcasts a code to the slave controller if the cascaded interrupt won arbitration on the master controller. the slave controller compares this identification code to the value stored in its icw3, and if it matches, the slave controller assumes responsibility for broadcasting the interrupt vector. icw4 the final write in the sequence (icw4) must be programmed both controllers. at the very least, bit 0 must be set to a 1 to indicate that the controllers are operating in an intel architecture-based system. 5.7.3 operation command words (ocw) these command words reprogram the interrupt controller to operate in various interrupt modes. ? ocw1 masks and unmasks interrupt lines. ? ocw2 controls the rotation of interrupt priorities when in rotating priority mode and controls the eoi function. ? ocw3 is sets up isr/irr reads, enables/disables the special mask mode smm and enables/ disables polled interrupt mode. 82801BA ich2 and 82801BAm ich2-m datasheet 5-45 functional description 5.7.4 modes of operation fully nested mode in this mode, interrupt requests are ordered in priority from 0 through 7, with 0 being the highest. when an interrupt is acknowledged, the highest priority request is determined and its vector placed on the bus. additionally, the isr for the interrupt is set. this isr bit remains set until: the processor issues an eoi command immediately before returning from the service routine; or if in aeoi mode, on the trailing edge of the second inta#. while the isr bit is set, all further interrupts of the same or lower priority are inhibited; higher levels will generate another interrupt. interrupt priorities can be changed in the rotating priority mode. special fully nested mode this mode will be used in the case of a system where cascading is used and the priority has to be conserved within each slave. in this case, the special fully nested mode will be programmed to the master controller. this mode is similar to the fully nested mode with the following exceptions: ? when an interrupt request from a certain slave is in service, this slave is not locked out from the master's priority logic and further interrupt requests from higher priority interrupts within the slave will be recognized by the master and will initiate interrupts to the processor. in the normal nested mode, a slave is masked out when its request is in service. ? when exiting the interrupt service routine, software has to check whether the interrupt serviced was the only one from that slave. this is done by sending a non-specific eoi command to the slave and then reading its isr. if it is 0, a non-specific eoi can also be sent to the master. automatic rotation mode (equal priority devices) in some applications there are a number of interrupting devices of equal priority. automatic rotation mode provides for a sequential 8-way rotation. in this mode a device receives the lowest priority after being serviced. in the worst case a device requesting an interrupt will have to wait until each of seven other devices are serviced at most once. there are two ways to accomplish automatic rotation using ocw2; the rotation on non-specific eoi command (r=1, sl=0, eoi=1) and the rotate in automatic eoi mode which is set by (r=1, sl=0, eoi=0). specific rotation mode (specific priority) software can change interrupt priorities by programming the bottom priority. for example, if irq5 is programmed as the bottom priority device, irq6 will be the highest priority device. the set priority command is issued in ocw2 to accomplish this, where: r=1, sl=1, and lo-l2 is the binary priority level code of the bottom priority device. in this mode, internal status is updated by software control during ocw2. however, it is independent of the eoi command. priority changes can be executed during an eoi command by using the rotate on specific eoi command in ocw2 (r=1, sl=1, eoi=1 and lo?l2=irq level to receive bottom priority. poll mode poll mode can be used to conserve space in the interrupt vector table. multiple interrupts that can be serviced by one interrupt service routine do not need separate vectors if the service routine uses the poll command. polled mode can also be used to expand the number of interrupts. the polling interrupt service routine can call the appropriate service routine, instead of providing the interrupt functional description 5-46 82801BA ich2 and 82801BAm ich2-m datasheet vectors in the vector table. in this mode, the intr output is not used and the microprocessor internal interrupt enable flip-flop is reset, disabling its interrupt input. service to devices is achieved by software using a poll command. the poll command is issued by setting p=1 in ocw3. the pic treats its next i/o read as an interrupt acknowledge, sets the appropriate isr bit if there is a request, and reads the priority level. interrupts are frozen from the ocw3 write to the i/o read. the byte returned during the i/o read will contain a 1? in bit 7 if there is an interrupt, and the binary code of the highest priority level in bits 2:0. cascade mode the pic in the ich2 has one master 8259 and one slave 8259 cascaded onto the master through irq2. this configuration can handle up to 15 separate priority levels. the master controls the slaves through a 3-bit internal bus. in the ich2, when the master drives 010b on this bus, the slave controller takes responsibility for returning the interrupt vector. an eoi command must be issued twice: once for the master and once for the slave. edge-triggered and level-triggered mode in isa systems this mode is programmed using bit 3 in icw1, which sets level or edge for the entire controller. in the ich2, this bit is disabled and a new register for edge-triggered and level- triggered mode selection, per interrupt input, is included. this is the edge/level control registers elcr1 and elcr2. if an elcr bit is 0?, an interrupt request will be recognized by a low to high transition on the corresponding irq input. the irq input can remain high without generating another interrupt. if an elcr bit is 1?, an interrupt request will be recognized by a high level on the corresponding irq input and there is no need for an edge detection. the interrupt request must be removed before the eoi command is issued to prevent a second interrupt from occurring. in both the edge-triggered and level-triggered modes, the irq inputs must remain active until after the falling edge of the first internal inta#. if the irq input goes inactive before this time, a default irq7 vector will be returned. end of interrupt operations an eoi can occur in one of two fashions: by a command word write issued to the pic before returning from a service routine, the eoi command; or automatically when aeoi bit in icw4 is set to 1. normal end of interrupt in normal eoi, software writes an eoi command before leaving the interrupt service routine to mark the interrupt as completed. there are two forms of eoi commands: specific and non- specific. when a non-specific eoi command is issued, the pic will clear the highest isr bit of those that are set to 1. non-specific eoi is the normal mode of operation of the pic within the ich2, as the interrupt being serviced currently is the interrupt entered with the interrupt acknowledge. when the pic is operated in modes which preserve the fully nested structure, software can determine which isr bit to clear by issuing a specific eoi. an isr bit that is masked will not be cleared by a non-specific eoi if the pic is in the special mask mode. an eoi command must be issued for both the master and slave controller. automatic end of interrupt mode in this mode, the pic will automatically perform a non-specific eoi operation at the trailing edge of the last interrupt acknowledge pulse. from a system standpoint, this mode should be used only when a nested multi-level interrupt structure is not required within a single pic. the aeoi mode can only be used in the master controller and not the slave controller. 82801BA ich2 and 82801BAm ich2-m datasheet 5-47 functional description 5.7.5 masking interrupts masking on an individual interrupt request each interrupt request can be masked individually by the interrupt mask register (imr). this register is programmed through ocw1. each bit in the imr masks one interrupt channel. masking irq2 on the master controller will mask all requests for service from the slave controller. special mask mode some applications may require an interrupt service routine to dynamically alter the system priority structure during its execution under software control. for example, the routine may wish to inhibit lower priority requests for a portion of its execution but enable some of them for another portion. the special mask mode enables all interrupts not masked by a bit set in the mask register. normally, when an interrupt service routine acknowledges an interrupt without issuing an eoi to clear the isr bit, the interrupt controller inhibits all lower priority requests. in the special mask mode, any interrupts may be selectively enabled by loading the mask register with the appropriate pattern. the special mask mode is set by ocw3 where: ssmm=1, smm=1, and cleared where ssmm=1, smm=0. 5.7.6 steering pci interrupts the ich2 can be programmed to allow pirqa#?pirqh# to be internally routed to interrupts [3:7, 9:12, 14 or 15]. the assignment is programmable through the pirqx route control registers, located at 60?63h and 68?6bh in function 0. one or more pirqx# lines can be routed to the same irqx input. if interrupt steering is not required, the route registers can be programmed to disable steering. the pirqx# lines are defined as active low, level sensitive to allow multiple interrupts on a pci board to share a single line across the connector. when a pirqx# is routed to specified irq line, software must change the irq's corresponding elcr bit to level sensitive mode. the ich2 will internally invert the pirqx# line to send an active high level to the pic. when a pci interrupt is routed onto the pic, the selected irq can no longer be used by an isa device (through serirq). however, active low non-isa interrupts can share their interrupt with pci interrupts. functional description 5-48 82801BA ich2 and 82801BAm ich2-m datasheet 5.8 advanced interrupt controller (apic) (d31:f0) in addition to the standard isa compatible interrupt controller (pic) described in the previous section, the ich2 incorporates the advanced programmable interrupt controller (apic). while the standard interrupt controller is intended for use in a uni-processor system, apic can be used in either a uni-processor or multi-processor system. 5.8.1 interrupt handling the i/o apic handles interrupts very differently than the 8259. briefly, these differences are: ? method of interrupt transmission. the i/o apic transmits interrupts through a 3-wire bus and interrupts are handled without the need for the processor to run an interrupt acknowledge cycle. ? interrupt priority. the priority of interrupts in the i/o apic is independent of the interrupt number. for example, interrupt 10 can be given a higher priority than interrupt 3. ? more interrupts. the i/o apic in the ich2 supports a total of 24 interrupts. ? multiple interrupt controllers. the i/o apic interrupt transmission protocol has an arbitration phase that allows for multiple i/o apics in the system with their own interrupt vectors. the ich2 i/o apic must arbitrate for the apic bus before transmitting its interrupt message. 82801BA ich2 and 82801BAm ich2-m datasheet 5-49 functional description 5.8.2 interrupt mapping the i/o apic within the ich2 supports 24 apic interrupts. each interrupt has its own unique vector assigned by software. the interrupt vectors are mapped as follows and match ?configuration 6? of the multi-processor specification. table 5-18. apic interrupt mapping irq # via serirq direct from pin via pci message internal modules 0 no no no cascade from 8259 #1 1yes no yes 2 no no no 8254 counter 0 3yes no yes 4yes no yes 5yes no yes 6yes no yes 7yes no yes 8nononortc 9 yes no yes option for sci, tco 10 yes no yes option for sci, tco 11 yes no yes option for sci, tco 12 yes no yes 13 no no no ferr# logic 14 yes yes yes 15 yes yes yes 16 pirqa pirqa no 17 pirqb pirqb no ac?97 audio, modem, option for smbus 18 pirqc pirqc no 19 pirqd pirqd no usb #1 20 n/a pirqe yes lan, option for sci, tco 21 n/a pirqf yes option for sci, tco 22 n/a pirqg yes option for sci, tco 23 n/a pirqh yes usb #2, option for sci, tco functional description 5-50 82801BA ich2 and 82801BAm ich2-m datasheet 5.8.3 apic bus functional description 5.8.3.1 physical characteristics of apic the apic bus is a 3-wire synchronous bus connecting all i/o and local apics. two of these wires are used for data transmission and one wire is a clock. for bus arbitration, the apic uses only one of the data wires. the bus is logically a wire-or and electrically an open-drain connection providing for both bus use arbitration and arbitration for lowest priority. the apic bus speed can run from 16.67 mhz to 33 mhz. 5.8.3.2 apic bus arbitration the i/o apic uses one wire arbitration to win bus ownership. a rotating priority scheme is used for apic bus arbitration. the winner of the arbitration becomes the lowest priority agent and assumes an arbitration id of 0. all other agents, except the agent whose arbitration id is 15, increment their arbitration ids by one. the agent whose id was 15 will take the winner's arbitration id and will increment it by one. arbitration ids are changed only for messages that are transmitted successfully (except for the low priority messages). a message is transmitted successfully if no cs error or acceptance error was reported for that message. an apic agent can use two different priority schemes: normal or eoi. eoi has the highest priority. eoi priority is used to send eoi messages for level interrupts from a local apic to an i/o apic. when an agent requests the bus with eoi priority, all other agents requesting the bus with normal priorities will back off. when ich2 detects a bus idle condition on the apic bus and it has an interrupt to send over the apic bus, it drives a start cycle to begin arbitration, by driving bit 0 to a ?0? on an apicclk rising edge. it then samples bit 1. if bit 1 was a ?0?, then a local apic started arbitration for an eoi message on the same clock edge that the ich2 started arbitration. thus, the ich2 has lost arbitration and stops driving the apic bus. if the ich2 did not detect an eoi message start, it will start transferring its arbitration id, located in bits [27:24] of its arbitration id register (arbid). starting in cycle 2 through cycle 5, it will tri-state bit 0, and drive bit 1 to a ?0? if arbid[27] is a ?1?. if arbid[27] is a ?0?, it will also tri- state bit 1. at the end of each cycle, the ich2 samples the state of bit 1 on the apic bus. if the ich2 did not drive bit 1 (arbid[27] = ?0?) and it samples a ?0?, then another apic agent started arbitration for the apic bus at the same time as the ich2, and it has higher priority. the ich2 will stop driving the apic bus. table 5-19 describes the arbitration cycles. table 5-19. arbitration cycles cycle bit 1 bit 0 comment 1 eoi 0 bit 1 = 1: normal, bit 1 = 0: eoi 2not ( arbid[27] )1 arbitration id. if ich2 samples a different value than it sent, it lost arbitration. 3not ( arbid[26] )1 4not ( arbid[25] )1 5not ( arbid[24] )1 82801BA ich2 and 82801BAm ich2-m datasheet 5-51 functional description 5.8.3.3 bus message formats after bus arbitration, the winner is granted exclusive use of the bus and will drive its message. apic messages come in four formats determined by the delivery mode bits. these four messages are of different length and are known by all apics on the bus through the transmission of the delivery mode bits. eoi message for level-triggered interrupts eoi messages are used by local apics to send an eoi cycle occurring for a level-triggered interrupt to an i/o apic. this message is needed so that the i/o apic can differentiate between a new interrupt on the interrupt line versus the same interrupt on the interrupt line. the target of the eoi is given by the local apic through the transmission of the priority vector (v7 through v0) of the interrupt. upon receiving this message, the i/o apic resets the remote irr bit for that interrupt. if the interrupt signal is still active after the irr bit is reset, the i/o apic will treat it as a new interrupt. table 5-20. apic message formats message # of cycles delivery mode bits comments eoi 14 xxx end of interrupt transmission from local apic to i/o apic on level interrupts. eoi is known by the eoi bit at the start of arbitration. short 21 001, 010, 100, 101, 111 i/o apic delivery on fixed, nmi, smi, reset, extint, and lowest priority with focus processor messages. lowest priority 33 001 transmission of lowest priority interrupts when the status field indicates that the processor does not have focus. remote read 39 011 message from one local apic to another to read registers. table 5-21. eoi message cycle bit 1 bit 0 comments 1 0 0 eoi message 2?5 arbid 1 arbitration id 6not(v7)not(v6) interrupt vector bits v7 - v0 from redirection table register 7not(v5)not(v4) 8not(v3)not(v2) 9not(v1)not(v0) 10 not(c1) not(c0) check sum from cycles 6 - 9 11 1 1 postamble 12 not(a) not(a) status cycle 0 13 not(a1) not(a1) status cycle 1 14 1 1 idle functional description 5-52 82801BA ich2 and 82801BAm ich2-m datasheet short message short messages are used for the delivery of fixed, nmi, smi, reset, extint and lowest priority with focus processor interrupts. the delivery mode bits (m2-m0) specify the message. all short messages take 21 cycles including the idle cycle. notes: 1. if dm is 0 (physical mode), then cycles 15 and 16 are the apic id and cycles 13 and 14 are sent as ?1?. if dm is 1 (logical mode), then cycles 13 through 16 are the 8-bit destination field. the interpretation of the logical mode 8-bit destination field is performed by the local units using the destination format register. shorthands of "all-incl-self" and "all-excl-self" both use physical destination mode and a destination field containing apic id value of all ones. the sending apic knows whether it should (incl) or should not (excl) respond to its own message. 2. the checksum field is the cumulative add (mod 4) of all data bits (dm, m0-3, l, tm, v0-7,d0-7). the apic driving the message provides this checksum. this, in essence, is the lower two bits of an adder at the end of the message. 3. this cycle allows all apics to perform various internal computations based on the information contained in the received message. one of the computations takes the checksum of the data received in cycles 6 through 16 and compares it with the value in cycle 18. if any apic computes a different checksum than the one passed in cycle 17, then that apic will signal an error on the apic bus (?00?) in cycle 19. if this happens, all apics will assume the message was never sent and the sender must try sending the message again, which includes re-arbitrating for the apic bus. in lowest priority delivery when the interrupt has a focus processor, the focus processor will signal this by driving a ?01? during cycle 19. this tells all the other apics that the interrupt has been accepted, the arbitration is preempted, and short message format is used. cycle 19 and 20 indicates the status of the message (i.e., accepted, check sum error, retry or error). table 5-23 shows the status signal combinations and their meanings for all delivery modes. table 5-22. short message cycle bit 1 bit 0 comments 1 1 0 normal arbitration 2?5 arbid 1 arbitration id 6 not(dm) not(m2) dm 1 = destination mode from bit 11 of the redirection table register 7not(m1)not(m0) m2-m0 = delivery mode from bits 10:8 of the redirection table register 8 not(l) not(tm) l = level, tm = trigger mode 9not(v7)not(v6) interrupt vector bits v7?v0 from redirection table register 10 not(v5) not(v4) 11 not(v3) not(v2) 12 not(v1) not(v0) 13 not(d7) not(d6) destination field from bits 63:56 of redirection table register 1 14 not(d5) not(d4) 15 not(d3) not(d2) 16 not(d1) not(d0) 17 not(c1) not(c0) checksum for cycles 6?16 2 18 1 1 postamble 3 19 not(a) not(a) status cycle 0. see table 5-23 . 20 not(a1) not(a1) status cycle 1. see table 5-23 . 21 1 1 idle 82801BA ich2 and 82801BAm ich2-m datasheet 5-53 functional description table 5-23. apic bus status cycle definition delivery mode a comments a1 comments fixed, eoi 11 checksum ok 1x error 01 accepted 00 retry 10 error xx 01 error xx 00 checksum error xx nmi, smm, reset, extint 11 checksum ok 1x error 01 accepted 00 error 10 error xx 01 error xx 00 checksum error xx lowest priority 11 checksum ok: no focus processor 1x error 01 end and retry 00 go for low priority arbitration 10 error xx 01 checksum ok: focus processor xx 00 checksum error xx remote read 11 checksum ok xx 10 error xx 01 error xx 00 checksum error xx functional description 5-54 82801BA ich2 and 82801BAm ich2-m datasheet lowest priority without focus processor (fp) message this message format is used to deliver an interrupt in the lowest priority mode in which it does not have a focus process. cycles 1 through 21 for this message are same as for the short message discussed above. status cycle 19 identifies if there is a focus processor (10) and a status value of 11 in cycle 20 indicates the need for lowest priority arbitration. notes: 1. cycle 21 through 28 are used to arbitrate for the lowest priority processor. the processor that takes part in the arbitration drives the processor priority on the bus. only the local apics that have "free interrupt slots" will participate in the lowest priority arbitration. 2. cycles 29 through 32 are used to break tie in case two more processors have lowest priority. the bus arbitration ids are used to break the tie. table 5-24. lowest priority message (without focus processor) cycle bit 1 bit 0 comments 1 1 0 normal arbitration 2?5 arbid 1 arbitration id 6 not(dm) not(m2) dm = destination mode from bit 11 of the redirection table register 7 not(m1) not(m0) m2-m0 = delivery mode from bits 10:8 of the redirection table register 8 not(l) not(tm) l = level, tm = trigger mode 9not(v7)not(v6) interrupt vector bits v7?v0 from redirection table register 10 not(v5) not(v4) 11 not(v3) not(v2) 12 not(v1) not(v0) 13 not(d7) not(d6) destination field from bits 63:56 of redirection table register 14 not(d5) not(d4) 15 not(d3) not(d2) 16 not(d1) not(d0) 17 not(c1) not(c0) checksum for cycles 6?16 18 1 1 postamble 19 not(a) not(a) status cycle 0. 20 not(a1) not(a1) status cycle 1. 21 p7 1 inverted processor priority p7?p0 22 p6 1 23 p5 1 24 p4 1 25 p3 1 26 p2 1 27 p1 1 28 p0 1 29 arbid3 1 30 arbid2 1 31 arbid1 1 32 arbid0 1 33 s s status 34 1 1 idle 82801BA ich2 and 82801BAm ich2-m datasheet 5-55 functional description remote read message remote read message is used when a local apic wishes to read the register in another local apic. the message format is same as short message for the first 21 cycles. note: cycle 21 through 36 contain the remote register data. the status information in cycle 37 specifies if the data is good or not. remote read cycle is always successful (although the data may be valid or invalid) in that it is never retried. the reason for this is that remote read is a debug feature, and a "hung" remote apic that is unable to respond should not cause the debugger to hang. table 5-25. remote read message cycle bit 1 bit 0 comments 1 1 0 normal arbitration 2?5 arbid 1 arbitration id 6 not(dm) not(m2) dm = destination mode from bit 11 of the redirection table register 7 not(m1) not(m0) m2-m0 = delivery mode from bits 10:8 of the redirection table register 8 not(l) not(tm) l = level, tm = trigger mode 9not(v7)not(v6) interrupt vector bits v7 - v0 from redirection table register 10 not(v5) not(v4) 11 not(v3) not(v2) 12 not(v1) not(v0) 13 not(d7) not(d6) destination field from bits 63:56 of redirection table register 14 not(d5) not(d4) 15 not(d3) not(d2) 16 not(d1) not(d0) 17 not(c1) not(c0) checksum for cycles 6 - 16 18 1 1 postamble 19 not(a) not(a) status cycle 0. 20 not(a1) not(a1) status cycle 1. 21 d31 d30 remote register data 31-0 22 d29 d28 23 d27 d26 24 d25 d24 25 d23 d22 26 d21 d20 27 d19 d18 28 d17 d16 29 d15 d14 30 d13 d12 31 d11 d10 32 d09 d08 33 d07 d06 34 d05 d04 35 d03 d02 36 d01 d00 37 s s data status: 00 = valid, 11 = invalid 38 c c check sum for data d31-d00 39 1 1 idle functional description 5-56 82801BA ich2 and 82801BAm ich2-m datasheet 5.8.4 pci message-based interrupts 5.8.4.1 theory of operation the following scheme is only supported when the internal i/o(x) apic is used (rather than just the 8259). the ich2 supports the new method for pci devices to deliver interrupts as write cycles, rather than using the traditional pirq[a:d] signals. essentially, the pci devices are given a write path directly to a register that will cause the desired interrupt. this mode is only supported when the ich2?s internal i/o apic is enabled. upon recognizing the write from the peripheral, the ich2 sends the interrupt message to the processor using the i/o apic?s serial bus. the interrupts associated with the pci message-based interrupt method must be set up for edge- triggered mode (rather than level-triggered) since the peripheral only does the write to indicate the edge. the following sequence is used: 1. during pci pnp, the pci peripheral is first programmed with an address (message_address) and data value (message_data) that will be used for the interrupt message delivery. for the ich2, the message_address is the irq pin assertion register, which is mapped to memory location: fec0_0020h (same as apic). 2. to cause the interrupt, the pci peripheral requests the pci bus and when granted, writes the message_data value to the location indicated by the message_address. the message_data value indicates which interrupt occurred. this message_data value is a binary encoded. for example, to indicate that interrupt 7 should go active, the peripheral will write a binary value of 0000111. the message_data will be a 32-bit value, although only the lower 5 bits are used. 3. if the prq bit in the apic version register is set, the ich2 positively decodes the cycles (as a slave) in medium time. 4. the ich2 decodes the binary value written to message_address and sets the appropriate irr bit in the internal i/o apic. the corresponding interrupt must be set up for edge- triggered interrupts. the ich2 supports interrupts 00h through 23h. binary values outside this range will not cause any action. 5. after sending the interrupt message to the processor, the ich2 automatically clears the interrupt. because they are edge-tiggered, the interrupts that are allocated to the pci bus for this scheme may not be shared with any other interrupt (e.g., the standard pci pirq[a:d], those received via serirq#, or the internal level-triggered interrupts such as sci or tco). the ich2 ignores interrupt messages sent by pci masters that attempt to use irq[0,2,8, or 13]. 5.8.4.2 registers and bits associated with pci interrupt delivery capabilities indication the capability to support pci interrupt delivery will be indicated via acpi configuration techniques. this involves the bios creating a data structure that gets reported to the acpi configuration software. the operating system reads the prq bit in the apic version register to see if the ich2 is capable of support pci-based interrupt messages. as a precaution, the prq bit is not set if the xapic_en bit is not set. interrupt message register the pci devices all write their message into the irq pin assertion register, which is a memory- mapped register located at the apic base memory location + 20h. 82801BA ich2 and 82801BAm ich2-m datasheet 5-57 functional description 5.8.5 front-side interrupt delivery 5.8.5.1 theory of operation for processors that support front-side bus interrupt delivery, the ich2 has an option to let the integrated i/o apic behave as an i/o (x) apic. in this case, it delivers interrupt messages to the processor in a parallel manner, rather than using the i/o apic serial scheme. the ich2 is intended to be compatible with the i/o (x) apic specification, revision 1.1. this is done by the ich2 writing (via the hub interface) directly to a memory location that is snooped by the processor(s). the processor(s) snoop the cycle to know which one goes active. the processor enables the mode by setting the i/o apic enable (apic_en) bit and by setting the dt bit in the i/o apic id register. the following sequence is used: 1. when the ich2 detects an interrupt event (active edge for edge-triggered mode or a change for level-triggered mode), it sets or resets the internal irr bit associated with that interrupt. 2. internally, the ich2 requests to use the bus in a way the automatically flushes upstream buffers. this can be internally implemented similar to a dma device request. 3. the ich2 then delivers the message by performing a write cycle to the appropriate address with the appropriate data. the address and data formats are described below in section 5.8.5.5 . notes: 1. fsb interrupt delivery compatibility with processor clock control depends on the processor, not the ich2. 2. fsb interrupt delivery compatibility with processor clock control depends on the processor, not the ich2. 5.8.5.2 edge-triggered operation in this case, the ?assert message? is sent when there is an inactive-to-active edge on the interrupt. the ?deassert message? is not used. 5.8.5.3 level-triggered operation in this case, the ?assert message? is sent when there is an inactive-to-active edge on the interrupt. if after the eoi the interrupt is still active, then another ?assert message? is sent to indicate that the interrupt is still active. if the interrupt was active but goes inactive before the eoi is received, the ?deassert message? is sent. 3. 82801BAm (ich2-m): fsb is not recommended in a mobile environment. for ich2-m, if fsb interrupt delivery mode is used, the system cannot support intel ? speedstep tm technology, c2, c3, software clock throttling or hardware thermal throttling. functional description 5-58 82801BA ich2 and 82801BAm ich2-m datasheet 5.8.5.4 registers associated with front-side bus interrupt delivery capabilities indication the capability to support front-side bus interrupt delivery will be indicated via acpi configuration techniques. this involves bios creating a data structure that gets reported to the acpi configuration software. dt bit in the boot configuration register this enables the ich2 to deliver interrupts as memory writes. this bit is ignored if the apic mode is not enabled. 5.8.5.5 interrupt message format ich2 writes the message to pci (and to the host controller) as a 32-bit memory write cycle. it uses the formats shown in table 5-26 and table 5-27 for the address and data. : table 5-26. interrupt message address format bit description 31:20 will always be feeh 19:12 destination id: this is the same as bits 63:56 of the i/o redirection table entry for the interrupt associated with this message. 11:4 reserved (will always be 0) 3 redirection hint: this bit is used by the processor host bridge to allow the interrupt message to be redirected. 0 = the message will be delivered to the agent (processor) listed in bits 19:4. 1 = the message will be delivered to an agent with a lower interrupt priority this can be derived from bits 10:8 in the data field (see below). the redirection hint bit = 1 if bits 10:8 in the delivery mode field associated with corresponding interrupt are encoded as 001 (lowest priority). otherwise, the redirection hint bit = 0. 2 destination mode: this bit is used only the redirection hint bit = 1. if the redirection hint bit and the destination mode bit are both set to 1, the logical destination mode is used and the redirection is limited only to those processors that are part of the logical group as based on the logical id. 1:0 will always be 00. 82801BA ich2 and 82801BAm ich2-m datasheet 5-59 functional description table 5-27. interrupt message data format bit description 31:16 will always be 0000h. 15 trigger mode: same as the corresponding bit in the i/o redirection table for that interrupt. 1 = level 0 = edge. 14 delivery status: if using edge-triggered interrupts, then this bit will always be 1, since only the assertion is sent. if using level-triggered interrupts, then this bit indicates the state of the interrupt input. 1 = assert 0 = deassert 13:12 will always be 00 11 destination mode: same as the corresponding bit in the i/o redirection table for that interrupt. 1 = logical. 0 = physical. 10:8 delivery mode: this is the same as the corresponding bits in the i/o redirection table for that interrupt. 000 = fixed 100 = nmi 001 = lowest priority 101 = init 010 = smi/pmi 110 = reserved 011 = reserved 111 = extint 7:0 vector: this is the same as the corresponding bits in the i/o redirection table for that interrupt. functional description 5-60 82801BA ich2 and 82801BAm ich2-m datasheet 5.9 serial interrupt (d31:f0) ich2 supports a serial irq scheme. this allows a single signal to be used to report interrupt requests. the signal (used to transmit this information) is shared between the host, the ich2, and all peripherals that support serial interrupts. the signal line (serirq) is synchronous to pci clock and follows the sustained tri-state protocol that is used by all pci signals. this means that if a device has driven serirq low, it will first drive it high synchronous to pci clock and release it the following pci clock. the serial irq protocol defines this sustained tri-state signaling in the following fashion: ? s - sample phase. signal driven low ? r - recovery phase. signal driven high ? t - turn-around phase. signal released the ich2 supports a message for 21 serial interrupts. these represent the 15 isa interrupts (irq[0,1, 2:15]), the four pci interrupts, and the smi# and iochk# control signals. the serial irq protocol does not support the additional apic interrupts (20?23). 5.9.1 start frame the serial irq protocol has two modes of operation which affect the start frame. these two modes are: ? continuous, where the ich2 is solely responsible for generating the start frame ? quiet, where a serial irq peripheral is responsible for beginning the start frame. the mode that must first be entered when enabling the serial irq protocol is continuous mode. in this mode, the ich2 will assert the start frame. this start frame is 4, 6, or 8 pci clocks wide based upon the serial irq control register, bits 1:0 at 64h in device 31:function 0 configuration space. this is a polling mode. when the serial irq stream enters quiet mode (signaled in the stop frame), the serirq line remains inactive and pulled up between the stop and start frame until a peripheral drives the serirq signal low. the ich2 senses the line low and continues to drive it low for the remainder of the start frame. since the first pci clock of the start frame was driven by the peripheral in this mode, the ich2 drives the serirq line low for 1 pci clock less than in continuous mode. this mode of operation allows for a quiet and, therefore, lower power operation. 5.9.2 data frames once the start frame has been initiated, all of the serirq peripherals must start counting frames based on the rising edge of serirq. each of the irq/data frames has exactly 3 phases of 1 clock each: ? sample phase. during this phase, the serirq device drives serirq low if the corresponding interrupt signal is low. if the corresponding interrupt is high, the serirq devices tri-state the serirq signal. the serirq line remains high due to pull-up resistors. a low level during the irq0-1 and irq2-15 frames indicates that an active-high isa interrupt is not being requested, but a low level during the pci int[a:d], smi#, and iochk# frame indicates that an active-low interrupt is being requested. ? recovery phase. during this phase, the device drives the serirq line high if in the sample phase it was driven low. if it was not driven in the sample phase, it is tri-stated in this phase. ? turn-around phase. the device will tri-state the serirq line. 82801BA ich2 and 82801BAm ich2-m datasheet 5-61 functional description 5.9.3 stop frame after all data frames, a stop frame is driven by ich2. the serirq signal is driven low by ich2 for 2 or 3 pci clocks. the number of clocks is determined by the serirq configuration register. the number of clocks determines the next mode. 5.9.4 specific interrupts not supported via serirq there are three interrupts seen through the serial stream that are not supported by the ich2. these interrupts are generated internally and are not sharable with other devices within the system. these interrupts are: ? irq0. heartbeat interrupt generated off of the internal 8254 counter 0. ? irq8#. rtc interrupt can only be generated internally. ? irq13. floating point error interrupt generated off of the processor assertion of ferr#. ich2 ignores the state of these interrupts in the serial stream, and does not adjust their level based on the level seen in the serial stream. in addition, the interrupts irq14 and irq15 from the serial stream are treated differently than their isa counterparts. these two frames are not passed to the bus master ide logic. the bus master ide logic expects ide to be behind the ich2. table 5-28. stop frame explanation stop frame width next mode 2 pci clocks quiet mode. any serirq device may initiate a start frame 3 pci clocks continuous mode. only the host (ich2) may initiate a start frame functional description 5-62 82801BA ich2 and 82801BAm ich2-m datasheet 5.9.5 data frame format table 5-29 shows the format of the data frames. for the pci interrupts (a-d), the output from the ich2 is anded with the pci input signal. thus, the interrupt can be signaled via both the pci interrupt input signal and via the serirq signal (they are shared). table 5-29. data frame format data frame # interrupt clocks past start frame comment 1 irq0 2 ignored. irq0 can only be generated via the internal 8524 2irq1 5 3 smi# 8 causes smi# if low. sets the serirq_smi_sts bit. 4irq3 11 5irq4 14 6irq5 17 7irq6 20 8irq7 23 9 irq8 26 ignored. irq8# can only be generated internally or on isa. 10 irq9 29 11 irq10 32 12 irq11 35 13 irq12 38 14 irq13 41 ignored. irq13 can only be generated from ferr# 15 irq14 44 do not include in bm ide interrupt logic 16 irq15 47 do not include in bm ide interrupt logic 17 iochck# 50 same as isa iochck# going active. 18 pci inta# 53 drive pirqa# 19 pci intb# 56 drive pirqb# 20 pci intc# 59 drive pirqc# 21 pci intd# 62 drive pirqd# 82801BA ich2 and 82801BAm ich2-m datasheet 5-63 functional description 5.10 real time clock (d31:f0) the real time clock (rtc) module provides a battery backed-up date and time keeping device with two banks of static ram (128 bytes each); the first bank has 114 bytes for general purpose usage. three interrupt features are available: time of day alarm with once a second to once a month range, periodic rates of 122 us to 500 ms, and end of update cycle notification. seconds, minutes, hours, days, day of week, month, and year are counted. daylight savings compensation is optional. the hour is represented in twelve or twenty-four hour format, and data can be represented in bcd or binary format. the design is meant to be functionally compatible with the motorola* ms146818b. the time keeping comes from a 32.768 khz oscillating source, which is divided to achieve an update every second. the lower 14 bytes on the lower ram block has very specific functions. the first ten are for time and date information. the next four (0ah to 0dh) are registers that configure and report rtc functions. the time and calendar data should match the data mode (bcd or binary) and hour mode (12 or 24 hour) as selected in register b. it is up to the programmer to make sure that data stored in these locations is within the reasonable values ranges and represents a possible date and time. the exception to these ranges is to store a value of c0?ffh in the alarm bytes to indicate a don?t care situation. all alarm conditions must match to trigger an alarm flag, which could trigger an alarm interrupt, if enabled. the set bit must be 1 while programming these locations to avoid clashes with an update cycle. access to time and date information is done through the ram locations. if a ram read from the ten time and date bytes is attempted during an update cycle, the value read will not necessarily represent the true contents of those locations. any ram writes under the same conditions will be ignored. note: the ich2 supports the ability to generate an smi# based on year 2000 rollover. see section 5.10.4 for more information on the century rollover. the ich2 does not implement month/year alarms. 5.10.1 update cycles an update cycle occurs once a second, if the set bit of register b is not asserted and the divide chain is properly configured. during this procedure, the stored time and date is incremented, overflow checked, a matching alarm condition checked, and the time and date are rewritten to the ram locations. the update cycle starts at least 488 us after the uip bit of register a is asserted and the entire cycle does not take more than 1984 us to complete. the time and date ram locations (0?9) are disconnected from the external bus during this time. to avoid update and data corruption conditions, external ram access to these locations can safely occur at two times. when a updated-ended interrupt is detected, almost 999 ms is available to read and write the valid time and date data. if the uip bit of register a is detected to be low, there is at least 488 us before the update cycle begins. warning: the overflow conditions for leap years and daylight savings adjustments are based on more than one date or time item. to ensure proper operation when adjusting the time, the new time and data values should be set at least two seconds before one of these conditions (leap year, daylight savings time adjustments) occurs. functional description 5-64 82801BA ich2 and 82801BAm ich2-m datasheet 5.10.2 interrupts the real-time clock interrupt is internally routed within the ich2 both to the i/o apic and the 8259. it is mapped to interrupt vector 8. this interrupt does not leave the ich2, nor is it shared with any other interrupt. irq8# from the serirq stream is ignored. 5.10.3 lockable ram ranges the rtc?s battery-backed ram supports two 8-byte ranges that can be locked via the configuration space. if the locking bits are set, the corresponding range in the ram are not readable or writable. a write cycle to those locations has no effect. a read cycle to those locations does not return the location?s actual value (may be all 0s or all 1s). once a range is locked, the range can be unlocked only by a hard reset, which invokes bios and allows it to relock the ram range. 5.10.4 century rollover ich2 detects a rollover when the year byte (rtc i/o space, index offset 09h) transitions form 99 to 00. upon detecting the rollover, the ich2 sets the newcentury_sts bit (tcobase + 04h, bit 7). if the system is in an s0 state, this causes an smi#. the smi# handler can update registers in the rtc ram that are associated with century value. if the system is in a sleep state (s1?s5) when the century rollover occurs, the ich2 also sets the newcentury_sts bit; no smi# is generated. when the system resumes from the sleep state, bios should check the newcentury_sts bit and update the century value in the rtc ram. 5.10.5 clearing battery-backed rtc ram clearing cmos ram in an ich2-based platform can be done by using a jumper on rtcrst# or gpi or using the safemode strap. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. using rtcrst# to clear cmos a jumper on rtcrst# can be used to clear cmos values, as well as reset to default, the state of the configuration bits that reside in the rtc power well. when the rtcrst# is strapped to ground, the rtc_pwr_sts bit (d31:f0:a4h bit 2) is set and the configuration bits in the rtc power well are set to their default state. bios can monitor the state of this bit and manually clear the rtc cmos array once the system is booted. the normal position would cause rtcrst# to be pulled up through a weak pull-up resistor. table 5-30 shows which bits are set to their default state when rtcrst# is asserted. rtcrst# should be used to reset configuration bits (and signal bios to clear cmos) only in a g3 state. additionally, rtcrst# assertion while power is on must only be done to invoke the test modes, and that it should only be asserted for the specific number of clocks to invoke the desired test mode. assertion for any other number of clocks may put the component into an indeterminate state, which is not supported. 82801BA ich2 and 82801BAm ich2-m datasheet 5-65 functional description using a gpi to clear cmos a jumper on a gpi can also be used to clear cmos values. bios detects the setting of this gpi on system boot-up and manually clear the cmos array. using the safemode strap to clear cmos a jumper on ac_sdout (safemode strap) can also be used to clear cmos values. bios detects the setting of the safe_mode status bit (d31:f0: offset d4h bit 2) on system boot-up, and manually clear the cmos array. note: both the gpi and safemode strap techniques to clear cmos require multiple steps to implement. the system is booted with the jumper in a new position, then powered back down. the jumper is replaced back to the normal position, then the system is rebooted again. the rtcrst# jumper technique allows the jumper to be moved and then replaced, all while the system is powered off. then, once booted, the rtc_pwr_sts can be detected in the set state. note: clearing cmos, using a jumper on vccrtc, must not be implemented. table 5-30. configuration bits reset by rtcrst# assertion bit name register location bits default value freq_strap[3:0] gen_sts d31:f0:d4h 11:8 1111b aie rtc reg b i/o space 5 0 af rtc reg c i/o space 5 0 pwr_flr gen_pmcon_3 d31:f0:a4h 1 0 afterg3_en gen_pmcon_3 d31:f0:a4h 0 0 rtc_pwr_sts gen_pmcon_3 d31:f0:a4h 2 1 prbtnor_sts pm1_sts pmbase + 00h 11 0 pme_en gpe0_en pmbase + 2ah 11 0 ri_en gpe0_en pmbase + 2ah 8 0 new_century_sts tco1_sts tcobase + 04h 7 0 intrd_det tco2_sts tcobase + 06h 0 0 top_swap gen_sts d31:f0:d4h 13 0 rtc_en pm1_en pmbase + 02h 10 0 batlow_en (ich2-m only) gpe0_en pmbase + 2ah 10 0 functional description 5-66 82801BA ich2 and 82801BAm ich2-m datasheet 5.11 processor interface (d31:f0) the ich2 interfaces to the processor with a variety of signals: ? standard outputs to the processor: a20m#, smi#, nmi, init#, intr, stpclk#, ignne#, cpuslp# ? standard input from the processor: ferr# most ich2 outputs to the processor use standard buffers. the ich2 has a separate vcc signal that is pulled up at the system level to the processor voltage and thus, determines voh for the outputs to the processor. note that this is different than previous generations of chips that have used open- drain outputs. this new method saves up to 12 external pull-up resistors. the ich2 also handles the speed setting for the processor by holding specific signals at certain states just prior to cpurst going inactive. this avoids the glue often required with other chipsets. the ich2 does not support the processor?s frc mode. 5.11.1 processor interface signals this section describes each of the signals that interface between the ich2 and the processor(s). note that the behavior of some signals may vary during processor reset, as the signals are used for frequency strapping. 5.11.1.1 a20m# the a20m# signal is active (low) when both of the following conditions are true: ? the alt_a20_gate bit (bit 1 of port92 register) is a 0 ? the a20gate input signal is a 0 the a20gate input signal is expected to be generated by the external microcontroller (kbc). 5.11.1.2 init# the init# signal is active (driven low) based on any one of several events described in table 5-31 . when any of these events occur, init# is driven low for 16 pci clocks, then driven high. note: the 16-clock counter for init# assertion halts while stpclk# is active. therefore, if init# is supposed to go active while stpclk# is asserted, it actually goes active after stpclk# goes inactive. ? for ich2-m, intel ? speedstep tm output to the processor: cpupwrgood 82801BA ich2 and 82801BAm ich2-m datasheet 5-67 functional description 5.11.1.3 ferr#/ignne# (coprocessor error) the ich2 supports the coprocessor error function with the ferr#/ignne# pins. the function is enabled via the coproc_err_en bit (device 31:function 0, offset d0, bit 13). ferr# is tied directly to the coprocessor error signal of the processor. if ferr# is driven active by the processor, irq13 goes active (internally). when it detects a write to the coproc_err register, the ich2 negates the internal irq13 and drives ignne# active. ignne# remains active until ferr# is driven inactive. ignne# is never driven active unless ferr# is active. if coproc_err_en is not set, the assertion of ferr# will not generate an internal irq13; the write to f0h will not generate ignne#. 5.11.1.4 nmi non-maskable interrupts (nmis) can be generated by several sources, as described in table 5-32 . table 5-31. init# going active cause of init# going active comment shutdown special cycle from the processor. port92 write, where init_now (bit 0) transitions from a 0 to a 1. portcf9 write, where rst_cpu (bit 2) was a 0 and sys_rst(bit 1) transitions from 0 to 1. rcin# input signal goes low. rcin# is expected to be driven by the external microcontroller (kbc). 0 to 1 transition on rcin# must occur before the ich2 arms init# to be generated again. processor bist to enter bist, the software sets cpu_bist_en bit and then does a full processor reset using the cf9 register. figure 5-12. coprocessor error timing diagram ferr# internal irq13 i/o write to f0h ignne# table 5-32. nmi sources cause of nmi comment serr# goes active (either internally, externally via serr# signal, or via message from mch) can instead be routed to generate an sci, through the nmi2sci_en bit (device 31:function 0, offset 4e, bit 11). iochk# goes active via serirq# stream (isa system error) can instead be routed to generate an sci, through the nmi2sci_en bit (device 31:function 0, offset 4e, bit 11). functional description 5-68 82801BA ich2 and 82801BAm ich2-m datasheet 5.11.1.5 stpclk# and cpuslp# signals the ich2 power management logic controls these active-low signals. refer to section 5.12 for more information on the functionality of these signals. 5.11.1.6 cpupwrgood signal this signal is connected to the processor?s pwrgood input. this is an open-drain output signal (external pull-up resistor required) that represents a logical and of the ich2?s pwrok and vrmpwrgd (vgate/vrmpwrgd for ich2-m) signals. 5.11.2 dual processor issues (82801BA ich2 only) 5.11.2.1 signal differences (82801BA ich2 only) 5.11.2.2 power management (82801BA ich2 only) 82801BAm ich2-m: for intel ? speedstep tm technology support, this signal is kept high during a intel ? speedstep tm state transition to prevent loss of processor context. in dual-processor designs, some of the processor signals are unused or used differently than for uniprocessor designs. table 5-33. dp signal differences (82801BA ich2 only) signal difference a20m# / a20gate generally not used, but still supported by the 82801BA ich2. stpclk# used for s1 state as well as preparation for entry to s3?s5 also allows for therm# based throttling (not via acpi control methods). should be connected to both processors. ferr# / ignne# generally not used, but still supported by 82801BA ich2. for the 82801BA ich2, attempting clock control with more than one processor is not feasible. this is because the host controller does not provide any indication as to which processor is executing a particular stop-grant cycle. without this information, there is no way for the ich2 to know when it is safe to deassert stpclk#. because the s1 state has the stpclk# signal active, the stpclk# signal can be connected to b oth processors. however, for acpi implementations, the ich2 does not support the c2 state for b oth processors, since there are not two processor control blocks. bios must indicate that the ich2 only supports the c1 state for dual-processor designs. however, the thrm# signal can be used for overheat conditions to activate thermal throttling. when entering s1, the ich2 asserts stpclk# to both processors. to meet the processor specifications, the cpuslp# signal has to be delayed until the 2 nd stop-grant cycle occurs. to ensure this, the ich2 waits a minimum or 60 pci clocks after receipt of the first stop-grant cycle b efore asserting cpuslp# (if the slp_en bit is set to 1). 82801BA ich2 and 82801BAm ich2-m datasheet 5-69 functional description 5.11.3 speed strapping for processor the ich2 directly sets the speed straps for the processor, saving the external logic that has been needed with prior pcisets. refer to the processor specification for speed strapping definition. the ich2 performs the following to set the speed straps for the processor: 1. while pwrok is active, the ich2 drives a20m#, ignne#, nmi, and intr high. 2. as soon as pwrok goes active, the ich2 reads the freq_strap field contents. 3. the next step depends on the power state being exited as described in table 5-34 . note: the freq_strap register is in the rtc well. the value in the register can be forced to 1111 via a pinstrap (ac_sdout signal), or the ich2 can automatically force the speed strapping to 1111 if the processor fails to boot. both processors must immediately respond to the stpclk# assertion with stop grant acknowledge cycles before the 82801BA ich2 asserts cpuslp# to meet the processor setup time for cpuslp#. meeting the processor setup time for cpuslp# is not an issue if both processors are idle when the system is entering s1. if it cannot be guaranteed that both processors will be idle, the slp_en bit must not be enabled. note that setting slp_en to 1 is not required to support s1 in a dual-processor configuration. in going to the s3, s4, or s5 states, the system will appear to pass through the s1 state and thus, stpclk# and slp# are also used. during the s3, s4, and s5 states, both processors will lose p ower. upon exit from those states, the processors will have their power restored. table 5-34. frequency strap behavior based on exit state state exiting ich2 s1 there is no processor reset, so no frequency strap logic is used. s3, s4, s5, or g3 based on pwrok going active, the ich2 deasserts pcirst#, and based on the value of the freq_strap field (d31:f0,offset d4), the ich2 drives the intended core frequency values on a20m#, ignne#, nmi, and intr. the ich2 holds these signals for 120 ns after cpurst# is deasserted by the host controller. table 5-35. frequency strap bit mapping freq_strap bits [3:0] sets high/low level for the corresponding signal 3nmi 2intr 1 ignne# 0 a20m# functional description 5-70 82801BA ich2 and 82801BAm ich2-m datasheet figure 5-13. signal strapping host controller cpu ich 4x 2 to 1 mux cpurst# pwrok pcirst# a20m#, igne#, intr, nmi init# freq. strap reg processor ich2 82801BA ich2 and 82801BAm ich2-m datasheet 5-71 functional description 5.12 power management (d31:f0) features ? acpi power and thermal management support ? acpi 24-bit timer ? software initiated throttling of processor performance for thermal and power reduction ? hardware override to throttle processor performance if system too hot ? sci and smi# generation ? pci pme# signal for wake up from low-power states ? system clock control ? system sleeping state control ? acpi s1 state: like c2 state (only stpclk# active, and slp# optional) ? acpi s3 state - suspend to ram (str) ? acpi s4 state - suspend-to-disk (std) ? acpi g2/s5 state - soft off (soff) ? power failure detection and recovery ? streamlined legacy power management support for apm-based systems ? acpi c2 state: stop-grant (or quickstart for the 82801BAm ich2-m) state (using stpclk# signal) halts processor?s instruction stream ? acpi c3 state (82801BAm ich2-m): ability to halt processor clock (but not hub interface or memory clock) ? 82801BAm ich2-m: clkrun# protocol for pci clock starting/stopping ? acpi s1 state (82801BA ich2): like c2 state (only stpclk# active, and slp# optional) ? acpi s1 state (82801BAm ich2-m): powered on suspend (pos) ? 82801BAm ich2-m: intel ? speedstep tm transition logic functional description 5-72 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.1 ich2 and system power states table 5-36 shows the power states defined for ich2-based platforms. the state names generally match the corresponding acpi states. table 5-37 shows the transitions rules among the various states. note that transitions among the various states may appear to temporarily transition through intermediate states. for example, in going from s0 to s1, it may appear to pass through the g0/s0/c2 states. these intermediate transitions and states are not listed in the table. table 5-36. general power states for systems using ich2 state/ substates legacy name / description g0/s0/c0 full on: processor operating. individual devices may be shut down to save power. the different processor operating levels are defined by cx states, as shown in table 5-37 . within the c0 state, the ich2 can throttle the stpclk# signal to reduce power consumption. the throttling can be initiated by software or by the thrm# input signal. g0/s0/c1 auto-halt: the processor has executed an autohalt instruction and is not executing code. the processor snoops the bus and maintains cache coherency. g0/s0/c2 stop-grant (ich2) / quickstart (ich2-m): the stpclk# signal goes active to the processor. the processor performs a stop-grant cycle, halts its instruction stream, and remains in that state until the stpclk# signal goes inactive. in the stop-grant (ich2) / quickstart (ich2-m) state, the processor snoops the bus and maintains cache coherency. g0/s0/c3 (ich2-m only) stop-clock: the stpclk# signal goes active to the processor. the processor performs a stop-grant cycle, halts its instruction stream. ich2-m then asserts stp_cpu#, which forces the clock generator to stop the processor clock. this is also used for intel ? speedstep tm technology support. accesses to memory (by agp, pci, or internal units) is not permitted while in a c3 state. it is assumed that the arb_dis bit is set prior to entering c3 state. g1/s1 (ich2 only) stop-grant: similar to g0/s0/c2 state. the ich2 also has the option to assert the cpuslp# signal to further reduce processor power consumption. note: the behavior for this state is slightly different when supporting ia64 processors. g1/s1 (ich2-m only) powered-on-suspend (pos): in this state, all clocks (except the 32.768 khz clock) are stopped. the system context is maintained in system dram. power is maintained to pci, the processor, memory controller, memory, and all other criticial subsystems. note that this state does not preclude power being removed from non-essential devices (e.g., disk drives). g1/s3 suspend-to-ram (str): the system context is maintained in system dram, but power is shut off to non-critical circuits. memory is retained and refreshes continue. all clocks stop except rtc clock. g1/s4 suspend-to-disk (std): the context of the system is maintained on the disk. all power is then shut off to the system except for the logic required to resume. externally appears same as s5, but may have different wake events. g2/s5 soft off (soff): system context is not maintained. all power is shut off except for the logic required to restart. a full boot is required when waking. g3 mechanical off (moff): system context not maintained. all power is shut off except for the rtc. no ?wake? events are possible, because the system does not have any power. this state occurs if the user removes the batteries, turns off a mechanical switch, or if the system power supply is at a level that is insufficient to power the ?waking? logic. when system power returns, transition depends on the state just prior to the entry to g3 and the afterg3 bit in the gen_pmcon3 register (d31:f0, offset a4). refer to ta b l e 5 - 4 5 for more details. 82801BA ich2 and 82801BAm ich2-m datasheet 5-73 functional description notes: 1. some wake events can be preserved through power failure. table 5-37. state transition rules for ich2 present state transition trigger next state g0/s0/c0 ? processor halt instruction ? level 2 read ? level 3 read ? slp_en bit set ? power button override ? mechanical off/power failure ?g0/s0/c1 ?g0/s0/c2 ?g0/s0/c3 ? g1/sx or g2/s5state ?g2/s5 ?g3 g0/s0/c1 ? any enabled break event ? stpclk# goes active ? power button override ? power failure ?g0/s0/c0 ?g0/s0/c2 ?g2/s5 ?g3 g0/s0/c2 ? any enabled break event ? stpclk# goes inactive and previously in c1 ? power button override ? power failure ?g0/s0/c0 ?g0/s0/c1 ?g2/s5 ?g3 g0/s0/c3 (ich2-m only) ? any enabled break event ? stpclk# goes inactive and previously in c1 ? power button override ? power failure ?g0/s0/c0 ?g0/s0/c1 ?g2/s5 ?g3 g1/s1, g1/s3, or g1/s4 ? any enabled wake event ? power button override ? power failure ? g0/s0/c0 (for ich2-m, see note 2) ?g2/s5 ?g3 g2/s5 ? any enabled wake event ? power failure ? g0/s0/c0 (for ich2-m, see note 2) ?g3 g3 ? power returns ? optional to go to s0/c0 (reboot) or g2/ s5 (stay off until power button pressed or other wake event). (for ich2 and ich2-m, see note 1) (for ich2-m, see note 2) 2. 82801BAm ich2-m, transitions from the s1-s5 or g3 states to the s0 state are deferred until batlow# is inactive. functional description 5-74 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.2 system power planes the system has several independent power planes, as described in table 5-38 . note that when a particular power plane is shut off, it should go to a 0v level. s 5.12.3 ich2 power planes the ich2 power planes were previously defined in section 3.1 . although not specific power planes within the ich2, there are many interface signals that go to devices that may be powered down. these include: ? ide: ich2 can tri-state or drive low all ide output signals and shut off input buffers. ? usb: ich2 can tri-state usb output signals and shut off input buffers if usb wakeup is not desired ? ac?97: ich2 can drive low the outputs and shut off inputs 5.12.4 smi#/sci generation upon any smi# event taking place, ich2 asserts smi# to the processor which causes it to enter smm space. smi# remains active until the eos bit is set. when the eos bit is set, smi# goes inactive for a minimum of 4 pciclks. if another smi event occurs, smi# is driven active again. the sci is a level-mode interrupt that is typically handled by an acpi-aware operating system. in non-apic systems (the default), the sci irq is routed to one of the 8259 interrupts (irq[9,10, or 11]). the 8259 interrupt controller must be programmed to level mode for that interrupt. in systems using the apic, the sci can still be routed to irq[9, 10, or 11] or it can be instead routed to one of the apic interrupts 20:23. in the case where the sci is routed to irq[20, 21, 22, or 23], the interrupt generated internally is an active low level. the interrupt table 5-38. system power plane plane controlled by description cpu (ich2-m only) slp_s3# signal slp_s1# puts the clock generator into a low-power state, but does not cut the power to the processor. the slp_s3# signal can be used to cut the processor?s power completely. main slp_s3# signal when slp_s3# goes active, power can be shut off to any circuit not required to wake the system from the s3 state. since the s3 state requires that the memory context be preserved, power must be retained to the main memory. the processor, devices on the pci bus, lpc interface, downstream hub interface and agp will typically be shut off when the main power plane is shut, although there may be small subsections powered. memory slp_s5# signal when the slp_s5# goes active, power can be shut off to any circuit not required to wake the system from the s4 or s5 state. since the memory context does not need to be preserved in the s5 state, the power to the memory can also be shut down. device[n] gpio individual subsystems may have their own power plane. for example, gpio signals may be used to control the power to disk drives, audio amplifiers, or the display screen. 82801BA ich2 and 82801BAm ich2-m datasheet 5-75 functional description remains low until all sci sources are removed. in the case where the sci is routed to irq[9, 10, or 11], the interrupt generated internally is active high. the interrupt remains high until all sci sources are removed. table 5-39 shows which events can cause an smi# and sci. note that some events can be programmed to cause either an smi# or sci. the usage of the event for sci (instead of smi#) is typically associated with an acpi-based system. each smi# or sci source has a corresponding enable and status bits. table 5-39. causes of smi# and sci cause sci smi additional enables where reported comment pme# yes yes pme_en=1 pme_sts can also cause wake event power button press yes yes pwrbtn_en=1 pwrbtn_sts can also cause wake event rtc alarm yes yes rtc_en=1 rtc_sts ring indicate yes yes ri_en=1 ri_sts ac?97 wakes yes yes ac97_en=1 ac97_sts usb#1 wakes yes yes usb1_en=1 usb1_sts usb#2 wakes yes yes usb2_en=1 usb2_sts thrm# pin active yes yes thrm_en=1 thrm_sts the thrm# can cause an smi# or sci on either the rising or falling edge. causes sci if sci_en is set, causes smi# if sci_en not set. acpi timer overflow (2.34 sec.) yes yes tmrof_en=1 tmrof_sts any gpi yes yes gpi[x]_route=10 (sci) gpi[x]_route=01 (smi) gpe1[x]_en=1 gpi[x]_sts gpe1_sts tco sci logic yes no tcosci_en=1 tcosci_sts can also cause irq (other than sci). tco sci message from mch yes no none mchsci_sts tco smi logic no yes tco_en=1 tco_sts can also cause irq (other than sci). tco smi: year 2000 rollover no yes none newcentury_sts tco smi: tco timerout no yes none timeout tco smi: os writes to tco_dat_in register no yes none os_tco_smi tco smi: message from mch no yes none mchsmi_sts tco smi: nmi occurred (and nmi?s mapped to smi) no yes nmi2smi_en=1 nmi2smi_sts tco smi: intruder# signal goes active no yes intrd_sel=10 intrd_det functional description 5-76 82801BA ich2 and 82801BAm ich2-m datasheet notes: tco smi: change of the bioswp bit from 0 to 1 no yes bld=1 bioswr_sts tco smi: write attempted to bios no yes bioswp=1 bioswr_sts bios_rls writen to yes no gbl_en=1 gbl_sts acpi code in os sets gbl_rls bit to cause bios_sts bit active, which causes smi#. gbl_rls written to no yes bios_en=1 bios_sts this bit is set when the bios sets the bios_rls bit. the acpi handler will clear the bit. write to b2h register no yes none apm_sts os or bios writes to the apmc register. smm handler clears. periodic timer expires no yes periodic_en=1 periodic_sts 64 ms timer expires no yes swsmi_tmr_en=1 swsmi_tmr_sts allows smm handler to exit temporarily. another smi# occurs about 64 ms later. legacy usb logic no yes legacy_usb_en=1 legacy_usb_sts bit set based on address decode or incoming usb irq. serial irq smi reported no yes none serirq_smi_sts device trap: device monitors match address in its range no yes dev[n]_trap_en=1 devmon_sts, dev[n]_trap_sts indicates that subsystems may need to be powered back on. smbus host controller no yes smb_smi_en smbus host status reg. smbus slave smi no yes none smbus_smi_sts batlow# assertion (ich2-m) yes ye s batlow_en=1. batlow_sts global standby timer expires in s1 state (ich2-m) yes no when activated, only counts when in the s1 state. access microcontroller 62h/66h no yes mcsmi_en mcsmi_sts access to microcontroller range (62h/66h) with mcsmi_en set. slp_en bit written to 1 no yes smi_on_slp_en=1 smi_on_slp_en_sts table 5-39. causes of smi# and sci (continued) cause sci smi additional enables where reported comment 1. sci_en must be 1 to enable sci. sci_en must be 0 to enable smi. 2. sci can be routed to cause interrupt 9:11 or 20:23 (20:23 only available in apic mode). 3. gbl_smi_en must be 1 to enable smi. 4. eos must be written to 1 to re-enable smi for the next one. 5. the gpi[x]_ route bits can enable gpis to generate smis regardless of the state of smi_en. 82801BA ich2 and 82801BAm ich2-m datasheet 5-77 functional description 5.12.5 dynamic processor clock control ich2 has extensive control for dynamically starting and stopping system clocks. the clock control is used for transitions among the various s0/cx states and processor throttling. each dynamic clock control method is described in this section. the various sleep states may also perform types of non- dynamic clock control. the ich2 supports the acpi c0, c1 and c2 states. the dynamic processor clock control is handled using the following signals: ? stpclk#: used to halt processor instruction stream. ? cpuslp#: must be asserted prior to stp_cpu# (in stop grant mode) the c1 state is entered based on the processor performing an autohalt instruction. the c2 state is entered based on the processor reading the level 2 register in the ich2. a c1 or c2 state (c1, c2, or c3 state for the 82801BAm ich2-m) ends due to a break event. based on the break event, the ich2-m returns the system to c0 state. table 5-40 lists the possible break events from c2 (c2 or c3 for the ich2-m). the break events from c1 are indicated in the processor?s datasheet. in addition to c0, c1, and c2 states, the 82801BAm ich2-m supports the acpi c3 states. ? c3_stat# (ich2-m only): used to signal an agp device that the system is about to enter, or has just exited a c3 state. ? stp_cpu# (ich2-m only): used to stop cpu?s clock for the ich2-m, the c3 state is entered based on the processor reading the level 3 register in the ich2-m. note that a intel ? speedstep tm transition may appear to temporarily pass through a c3 state; however, it is a separate transition and documented separately in ??. table 5-40. break events event breaks from comment any unmasked interrupt goes active c2 (ich2) c2, c2 (ich2-m) irq[0:15] when using the 8259s, irq[0:23] for i/o apic. since sci is an interrupt, any sci will also be a break event. any internal event that will cause an nmi or smi# c2 (ich2) c2, c3 (ich2-m) many possible sources any internal event that will cause init# to go active c2 (ich2) c2, c3 (ich2-m) could be indicated by the keyboard controller via the rcin input signal. any bus master request (internal, external or dma) goes active c3 only (ich2-m only) need to wake up processor so it can do snoops functional description 5-78 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.5.1 throttling using stpclk# throttling is used to lower power consumption or reduce heat. the ich2 asserts stpclk# to throttle the processor clock and the processor appears to temporarily enter a c2 state. after a programmable time, the ich2 deasserts stpclk# and the processor appears to return to the c0 state. this allows the processor to operate at reduced average power, with a corresponding decrease in performance. two methods are included to start throttling: ? software enables a timer with a programmable duty cycle. the duty cycle is set by the thtl_dty field and the throttling is enabled using the thtl_en field. this is known as manual throttling. the period is fixed to be in the non-audible range, due to the nature of switching power supplies. ? a thermal override condition (thrm# signal active for >2 seconds) occurs that unconditionally forces throttling, independent of the thtl_en bit. the throttling due to thermal override has a separate duty cycle (thrm_dty) which may vary by field and system. the thermal override condition will end when thrm# goes inactive. throttling due to the thrm# signal has higher priority than the software-initiated throttling. throttling does not occur when the system is in a c2 state (c2 or c3 for the ich2-m), even if thermal override occurs. 5.12.5.2 transition rules among s0/cx and throttling states the following priority rules and assumptions apply among the various s0/cx and throttling states: ? entry to any s0/cx state is mutually exclusive with entry to any s1?s5 state. this is because the processor can only perform one register access at a time and sleep states have higher priority than thermal throttling. ? when the slp_en bit is set (system going to a sleep state (s1?s5), the thtl_en bit can be internally treated as being disabled (no throttling while going to sleep state). note that thermal throttling (based on thrm# signal) cannot be disabled in an s0 state. however, once the slp_en bit is set, the thermal throttling is shut off (since stpclk# will be active in s1?s5 states). ? if the thtl_en bit is set, and a level 2 (level 2 or level 3 for the ich2-m) read then occurs, the system should immediately go and stay in a c2 (c2 or c3 for the ich2-m) state until a break event occurs. a level 2 (level 2 or level 3 for the ich2-m) read has higher priority than the software-initiated throttling or thermal throttling. ? if thermal override is causing throttling and a level 2 (level 2 or level 3 for the ich2-m) read then occurs, the system will stay in a c2 (c2 or c3 for the ich2-m) state until a break event occurs. a level 2 (level 2 or level 3 for the ich2-m) read has higher priority than the thermal override. ? after an exit from a c2 (c2 or c3 for the ich2-m) state (due to a break event), and if the thtl_en bit is still set, or if a thermal override is still occurring, the system will continue to throttle stpclk#. depending on the time of the break event, the first transition on stpclk# active can be delayed by up to one period. ? the host controller must post stop-grant cycles in such a way that the processor gets an indication of the end of the special cycle prior to the ich2 observing the stop-grant cycle. this ensures that the stpclk# signals stays active for a sufficient period after the processor observes the response phase. ? if in the c1 state and the stpclk# signal goes active, the processor will generate a stop- grant cycle, and the system should go to the c2 state. when stpclk# goes inactive, it should return to the c1 state. 82801BA ich2 and 82801BAm ich2-m datasheet 5-79 functional description 5.12.6 dynamic pci clock control (82801BAm ich2-m) 5.12.6.1 conditions for stopping the pci clock (82801BAm ich2-m) 5.12.6.2 conditions for maintaining the pci clock (82801BAm ich2-m) 5.12.6.3 conditions for stopping the pci clock (82801BAm ich2-m) for the ich2-m, the pci clock can be dynamically controlled independent of any other low- p ower state. this control is accomplished using the clkrun# protocol as described in the pci m obile design guide, and is transparent to software. the dynamic pci clock control is handled using the following signals: ? clkrun#: used by pci and lpc peripherals to request the system pci clock to run ? stp_pci#: used to stop the system pci clock n ote: the 33 mhz clock to the ich2-m is ?free-running? and is not affected by the stp_pci# signal. when there is a lack of pci activity, the ich2-m has the capability to stop the pci clocks to conserve power. ?pci activity? is defined as any activity that requires the pci clock to be running. any of the following conditions indicates that it is not ok to stop the pci clock: ? cycles on pci or lpc ? cycles of any internal device that would need to go on the pci bus ? cycles using pc/pci dma ? serirq activity behavioral descripion ? when there is a lack of activity (as defined above) for 29 pci clocks, the ich2-m deassert (drive high) clkrun# for 1 clock and then tri-state the signal. pci master that wish to maintain the pci clock running will observe the clkrun# signal deasserted, and then must re-assert if (drive it low) within 3 clocks. behavioral description ? when the ich2-m has tri-stated the clkrun# signal after deasserting it, the ich2-m then checks to see if the signal has been re-asserted (externally). ? after observing the clkrun# signal asserted for 1 clock, the ich2-m again starts asserting the signal. ? if an internal device needs the pci bus, the ich2-m asserts the clkrun# signal. behavioral description ? if no device re-asserts clkrun# once it has been deasserted for 3 clocks, the ich2-m stops the pci clock by asserting the stp_pci# signal to the clock synthesizer. functional description 5-80 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.6.4 conditions for re-starting the pci clock (82801BAm ich2-m) 5.12.6.5 other causes of clkrun# going active (82801BAm ich2-m) 5.12.6.6 lpc devices and clkrun# (82801BAm ich2-m) behavioral description ? a peripheral asserts clkrun# to indicate that it needs the pci clock re-started. ? when the ich2-m observes the clkrun# signal asserted for 1 (free running) clock, the ich2-m deasserts the stp_pci# signal to the clock synthesizer within 4 (free running) clocks. ? observing the clkrun# signal asserted externally for 1 (free running) clock, the ich2-m again starts driving clkrun# asserted. if an internal source requests the clock to be re-started, the ich2-m re-asserts clkrun#, and simultaneously deasserts the stp_pci# signal. the following causes the ich2-m to assert and/or maintain the clkrun# signal active (low): ? pc/pci activity, which is started by one of the reqx# signals going active. it is expected that a pc/pci device asserts clkrun# prior to starting the start bit on the req# signal. once the start bit is recognized, the ich2-m makes sure clkrun# goes active if it should go inactive during the sequence. ? serirq activity, which is started by the serirq signal going low (in quiet mode), or the serirq logic being in the continuous mode. it is expected that a serirq device asserts clkrun# prior to starting the start bit on the seirq signal. once the start bit is recognized, the ich2-m makes sure clkrun# goes active if it should go inactive during the sequence. ? any internal or external bus master request, including lpc masters. once the master request is detected (via pci req or lpc ldrq[1:0]#), the ich2-m maintains clkrun# active until the end of the sequence. this includes: ?any pci req# low ? bus master or dma request pending (having come in via ldrq[1:0]#) ? any cycle coming down from hub interface1 to pci ? any pci cycle currently in progress. for example, cycle forward by the ich2-m from the hub interface to pci, and then claimed by ich2-m's pci-to-lpc logic. that cycle runs as a delayed transaction on pci. clkrun# should stay low until the cycle completes (without delayed transaction). ? any bus master below pci that needs to run a cycle. this could include the front-side-bus interrupt logic for the i/o apic (if it is downstream of pci). if an lpc device (of any type) needs the 33 mhz pci clock (e.g., for lpc dma or lpc serial interrupt), it can assert clkrun#. note that lpc devices running dma or bus master cycles do not need to assert clkrun#, since the ich2-m asserts it on their behalf. 82801BA ich2 and 82801BAm ich2-m datasheet 5-81 functional description 5.12.7 sleep states the ich2 directly supports different sleep states (s1?s5), which are entered by setting the slp_en bit, or due to a power button press. the entry to the sleep states are based on several assumptions: ? entry to a cx state is mutually exclusive with entry to a sleep state. this is because the processor can only perform one register access at a time. a request to sleep always has higher priority than throttling. ? prior to setting the slp_en bit, the software turns off processor-controlled throttling. note that thermal throttling cannot be disabled, but setting the slp_en bit will disable thermal throttling (since s1?s5 sleep state has higher priority). ? the g3 state cannot be entered via any software mechanism. the g3 state indicates a complete loss of power. 5.12.7.1 initiating sleep state sleep states (s1?s5) are initiated by: ? masking interrupts, turning off all bus master enable bits, setting the desired type in the slp_typ field, and then setting the slp_en bit. the hardware will then attempt to gracefully put the system into the corresponding sleep state by first going to a c2 (c2 or c3 for the ich2-m) state. see section 5.12.5 for details on going to the c2 (c2 or c3 for the ich2-m) state. ? pressing the pwrbtn# signal for more than 4 seconds to cause a power button override event. in this case the transition to the s5 state will be less graceful, since there will be no dependencies on observing stop-grant cycles from the processor or on clocks other than the rtc clock. 5.12.7.2 exiting sleep states sleep states (s10?s5) are exited based on wake events. the wake events will force the system to a full on state (s0), although some non-critical subsystems might still be shut off and have to be brought back manually. for example, the hard disk may be shut off during a sleep state, and have to be enabled via a gpio pin before it can be used. table 5-41. sleep types sleep type comment s1 (ich2 only) ich2 asserts the cpuslp# signal. this lowers the processor?s power consumption. no snooping is possible in this state. s1 (ich2-m only) ich2-m asserts the slp_s1# signal. this can be connected to the system clock generator to either put it into a low-power mode or to remove its power altogether. no snooping is possible in this state. s3 ich2 asserts slp_s3# (ich2-m asserts slp_s1# and slp_s3#). the slp_s3# signal controls the power to non-critical circuits. power is only be retained to devices needed to wake from this sleeping state, as well as to the memory. s4 ich2 asserts slp_s3# and slp_s5# (ich2-m asserts slp_s1#, slp_s3# and slp_s5#). the slp_s5# signal shuts off the power to the memory subsystem. only devices needed to wake from this state should be powered. s5 same as s4. ich2 asserts slp_s3# and slp_s5# (ich2-m asserts slp_s1#, slp_s3# and slp_s5#). the slp_s5# signal shuts off the power to the memory subsystem. only devices needed to wake from this state should be powered. functional description 5-82 82801BA ich2 and 82801BAm ich2-m datasheet upon exit from the ich2-controlled sleep states, the wak_sts bit will be set. the possible causes of wake events (and their restrictions) are shown in table 5-42 . notes: ? if in the s5 state due to a powerbutton override, the only wake event is power button. notes: 1. this will be a wake event from s5 only if the sleep state was entered by setting the slp_en and slp_typ bits via software. it is important to understand that the various gpis have different levels of functionality when used as wake events. the gpis that reside in the core power well can only generate wake events from an s1 state. also, only certain gpis are ?acpi compliant,? meaning that their status and enable bits reside in acpi i/o space. table 5-43 summarizes the use of gpis as wake events. the latency to exit the various sleep states varies greatly and is heavily dependent on power supply design. approximations are shown in table 5-44 . the time indicates from when the wake event occurs (signal transition) to when the processor is allowed to start its first cycle (cpurst# goes inactive). there will be very large additional delays for the processor to execute sufficient amounts of bios to invoke the os (such as coming out of s1?s3) or spinning up the hard drive (e.g., coming out of s4 or s5). ? for the ich2-m, if the batlow# signal is asserted, the ich2-m will not attempt to wake from an s1 (mobile) ? s5 state, even if the power button is pressed. this prevents the system from waking when the battery power is insufficient to wake the system. wake events that occur while batlow# is asserted are latched by the ich2-m, and the system wakes after batlow# is deasserted. table 5-42. causes of wake events cause states can wake from how enabled rtc alarm s1 ? s5 (note 1) set rtc_en bit in pm1_en register power button s1 ? s5 always enabled as wake event gpi[0:n] s1 ? s5 (note 1) gpe1_en register usb s1 ? s4 set usb1_en and usb2_en bits in gpe0_en register lan s1 ? s5 will use pme#. wake enable set with lan logic. ri# s1 ? s5 (note 1) set ri_en bit in gpe0_en register ac97 s1 ? s5 set ac97_en bit in gpe0_en register pme# s1 ? s5 (note 1) set pme_en bit in gpe0_en register. gst timeout s1m setting the gst timeout range to a value other than 00h. smbalert# s1 ? s4 smb_wak_en in the gpe0 register smbus slave message s1 ? s5 always enabled as a wake event table 5-43. gpi wake events gpi power well wake from notes gpi[7:0], gpi[23:16] core s1 gpi[15:8] resume s1 ? s5 acpi compliant 82801BA ich2 and 82801BAm ich2-m datasheet 5-83 functional description 5.12.7.3 sx?g3?sx, handling power failures depending on when the power failure occurs and how the system is designed, different transitions can occur due to a power failure. the after_g3 bit provides the ability to program whether or not the system should boot once power returns after a power loss event. if the policy is to not boot, the system remains in an s5 state (unless previously in s4). there are only three possible events that will wake the system after a power failure. ? pwrbtn#: pwrbtn# is always enabled as a wake event. when rsmrst# is low (g3 state), the pwrbtn_sts bit is reset. when the ich2 exits g3 after power returns (rsmrst# goes high), the pwrbtn# signal is already high (because vcc-standby goes high before rsmrst# goes high) and the pwrbtn_sts bit is 0. ? ri#: ri# does not have an internal pull-up. therefore, if this signal is enabled as a wake event, it is important to keep this signal powered during the power loss event. if this signal goes low (active), when power returns, the ri_sts bit is set and the system interprets this as a wake event. ? rtc alarm: the rtc_en bit is in the rtc well and is preserved after a power loss. like pwrbtn_sts the rtc_sts bit is cleared when rsmrst# goes low. the ich2 monitors both pwrok and rsmrst# to detect power failures. if pwrok goes low, the pwrok_flr bit is set. if rsmrst# goes low, pwr_flr is set. note: although pme_en is in the rtc well, this signal cannot wake the system after a power loss. pme_en and pme_sts bits are cleared by rsmrst# table 5-44. sleep state exit latencies state latency s1 <1 ms. based on wake event to stpclk# high + re-enumeration of pci bus, usb, cardbus, etc. must also add pll spin-up times. s3 power supply ramp + 20 ms s4 power supply ramp + 20 ms s5 power supply ramp + 20 ms 82801BAm ich2-m: a power failure in a mobile system is a rare event, since the power subsystem should provide sufficient warning when the batteries are low. however, if the user removes the battery or leaves the system in an str state for too long, a power failure could occur. 82801BA ich2: in desktop systems, power failures can occur if the ac power is cut (a real power failure) or if the system is unplugged. in either case, pwrok and rsmrst# are assumed to go low. table 5-45. transitions due to power failure state at power failure afterg3_en bit transition when power returns s0, s1, s3 1 0 s5 s0 s4 1 0 s4 s0 s5 1 0 s5 s0 functional description 5-84 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.8 thermal management the ich2 has mechanisms to assist with managing thermal problems in the system. 5.12.8.1 thrm# signal the thrm# signal is used as a status input for a thermal sensor. based on the thrm# signal going active, the ich2 generates an smi# or sci (depending on sci_en). if the thrm_pol bit is set low, when the thrm# signal goes low, the thrm_sts bit will be set. this is an indicator that the thermal threshold has been exceeded. if the thrm_en bit is set, then when thrm_sts goes active, either an smi# or sci is generated (depending on the sci_en bit being set). the power management software (bios or acpi) can then take measures to start reducing the temperature. examples include shutting off unwanted subsystems, or halting the processor. by setting the thrm_pol bit to high, another smi# or sci can optionally be generated when the thrm# signal goes back high. this allows the software (bios or acpi) to turn off the cooling methods. 5.12.8.2 thrm# initiated passive cooling if the thrm# signal remains active for some time greater than 2 seconds and the ich2 is in the s0/g0/c0 state, then the ich2 enters an auto-throttling mode, in which it provides a duty cycle on the stpclk# signal. this will reduce the overall power consumption by the system, and should cool the system. the intended result of the cooling is that the thrm# signal should go back inactive. for all programmed values (001?111), thrm# going active will result in stpclk# active for a minimum time of 12.5% and a maximum of 87.5%. the period is 1024 pci clocks. thus, the stpclk# signal can be active for as little as 128 pci clocks or as much as 896 pci clocks. the actual slowdown (and cooling) of the processor will depend on the instruction stream, because the processor is allowed to finish the current instruction. furthermore, the ich2 waits for the stop- grant cycle before starting the count of the time the stpclk# signal is active. when thrm# goes inactive, throttling stops. in case that the ich2 is already attempting throttling because the thtl_en bit is set, the duty cycle associated with the thrm# signal will have higher priority. if the ich2 is in the c2 (c2 and c3 for the ich2-m) or s1?s5 states, then no throttling will be caused by the thrm# signal being active. 5.12.8.3 thrm# override software bit the force_thtl bit allows bios to force passive cooling, just as if the thrm# signal had been active for 2 seconds. if this bit is set, the ich2 starts throttling using the ratio in the thrm_dty field. when this bit is cleared, the ich2 stops throttling, unless the thrm# signal has been active for 2 seconds or if the thtl_en bit is set (indicating that acpi software is attempting throttling). 82801BA ich2 and 82801BAm ich2-m datasheet 5-85 functional description 5.12.8.4 processor-initiated passive cooling (via programmed duty cycle on stpclk#) using the thtl_en and thtl_dty bits, the ich2 can force a programmed duty cycle on the stpclk# signal. this reduces the effective instruction rate of the processor and cut its power consumption and heat generation. 5.12.8.5 active cooling active cooling involves fans. the gpio signals from the ich2 can be used to turn on/off a fan. 5.12.9 intel ? speedstep ? technology protocol (82801BAm ich2-m only) the intel ? speedstep ? technology feature enables a mobile system to operate in multiple p rocessor performance/thermal states and to transition smoothly between them. the internal p rocessor clock setting and processor supply voltage setting determines these states. the ich2-m supports one low power mode and one high performance mode. figure 5-14. intel ? speedstep ? block diagram (82801BAm ich2-m only) speedstep? enabled mobile intel ? processors processor's voltage regulator module (vrm) ich2-m cpuperf# cpupwrgd stpclk# vddcore vgate pw rok high voltage low voltage vrcode[4:0] from main power supply gmuxsel 5 5 5 functional description 5-86 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.9.1 intel ? speedstep? technology processor requirements (82801BAm ich2-m) 5.12.9.2 intel ? speedstep? technology states (82801BAm ich2-m) n on-intel ? speedstep ? technology processors use the a20m#, ignne#, nmi, and intr input signals to determine the multiplier used by the processor?s pll for the internal clock. in first- generation intel ? speedstep ? technology processors, two multiplier values (one for the high p erformance state, a second for the low power state) are hard-wired within the processor. the ich2-m cpuperf signal is used to select the processor state, based on ich2-m control logic. the operating bus ratio must be available to the programmer and is, therefore, suggested that it be read in a processor msr. also, the processor must return an indication that it is intel ? speedstep ? technology enabled, which should be in the form of a status bit in a processor msr or in the cpuid register. the ich2-m is not capable of determining whether it is attached to a intel ? speedstep ? or non- intel ? speedstep ? processor. when used with a non-intel ? speedstep ? processor, software should not write or read the ich2-m intel ? speedstep ? registers. the ich2-m supports two system-level performance states: low power mode and high performance mode. processor states are defined by valid combinations of core voltage levels and core clock speeds. these processor states can be used to alter the processor and system p erformance to conform to conditions of power and environment. the low power mode is used primarily when the system is powered from the battery, with the p urpose being to maximize battery life. mobile system performance is limited by thermal design and battery capacity. to improve thermal capacity, active cooling solutions (e.g., a fan can be used) in addition to a passive cooling solution. the high performance mode assume that the mobile system is powered from an external ac/dc source. the purpose of this state is to maximize performance subject to thermal constraints. the ich2-m does not implement any restrictions on entry into high performance mode. it will unconditionally transition into high performance mode upon software command. 82801BA ich2 and 82801BAm ich2-m datasheet 5-87 functional description 5.12.9.3 voltage regulator interface (82801BAm ich2-m) 5.12.10 event input signals and their usage the ich2 has various input signals that trigger specific events. this section describes those signals and how they should be used. 5.12.10.1 pwrbtn# ? power button the ich2 pwrbtn# signal operates as a ?fixed power button? as described in the acpi specification. pwrbtn# signal has a 16 ms de-bounce on the input. the state transition descriptions are included in the following table. note that the transitions start as soon as the pwrbtn# is pressed (but after the debounce logic), and does not depend on when the power button is released. the voltage regulator interface is critical to the intel ? speedstep ? technology concept. the p ower dissipation of the processor is proportional to the internal clock speed and to the square of the core supply voltage. as the internal clock speed of the processor changes, the minimum required core voltage supply level also changes. the interface signals are designed to allow the voltage regulator to change settings without causing a power-on reset. ? vrcode[4:0] is a 5-bit input to the voltage regulator. these signals are not outputs from the ich2-m; instead, they are outputs from an external muliplexer. future voltage regulators may integrate this multiplexer. ? the ssmuxsel# signal is an ich2-m output. it can be used directly to control the external muliplexer that selects the high or low values for vrcode[4:0]. ? vron (aka pwrok from main power supply) is an input to the regulator. when vron is asserted, the regulator turns on and settles to the output defined by vrcode[4:0]. vgate is an input from the regulator indicating that all of the outputs from the regulator are on and within specification. when the system is transitioning between performance states, the voltage regulator output may be required to change. it is not desirable, however, that cpupwrgood b ecomes deasserted during these transitions. normally, this would indicate to the system that a p ower-on reset be performed, which would invalidate the system context. the ich2-m prevents this from occurring by maintaining cpupwrgood during the transition. cpupwrgood must also be maintained during an s1 state. table 5-46. transitions due to power button present state event transition/action comment s0/cx pwrbtn# goes low smi# or sci generated (depending on sci_en) software will typically initiate a sleep state. s1 ? s5 pwrbtn# goes low wake event. transitions to s0 state. standard wakeup g3 pwrbtn# pressed none no effect since no power. not latched nor detected. s0 ? s4 pwrbtn# held low for at least 4 consecutive seconds unconditional transition to s5 state. no dependence on processor (such as stop-grant cycles) or any other subsystem. functional description 5-88 82801BA ich2 and 82801BAm ich2-m datasheet power button override function if pwrbtn# is observed active for at least 4 consecutive seconds, the state machine should unconditionally transition to the g2/s5 state, regardless of present state (s0?s4). in this case, the transition to the g2/s5 state should not depend on any particular response from the processor (e.g., a stop-grant cycle), nor any similar dependency from any other subsystem. the pwrbtn# status is readable to check if the button is currently being pressed or has been released. the status is taken after the de-bounce, and is readable via the pwrbtn_lvl bit. note: the 4-second pwrbtn# assertion should only be used if a system lock-up has occurred. the 4-second timer starts counting when the ich2 is in a s0 state. if the pwrbtn# signal is asserted and held active when the system is in a suspend state (s1?s5), the assertion causes a wake event. once the system has resumed to the s0 state, the 4-second timer starts. sleep button the acpi specification defines an optional sleep button. it differs from the power button in that it only is a request to go from s0 to s1?s4 (not s5). also, in an s5 state, the power button can wake the system, but the sleep button cannot. although the ich2 does not include a specific signal designated as a sleep button, one of the gpio signals can be used to create a ?control method? sleep button. see the acpi specification for implementation details. 5.12.10.2 ri# ? ring indicate the ring indicator can cause a wake event (if enabled) from the s1?s5 states. table 5-47 shows when the wake event is generated or ignored in different states. if in the g0/s0/cx states, the ich2 generates an interrupt based on ri# active and the interrupt is set up as a break event. note: filtering/debounce on ri# will not be done in ich2. can be in modem or external. 5.12.10.3 pme# ? pci power management event the pme# signal comes from a pci device to request that the system be restarted. the pme# signal can generate an smi#, sci, or optionally a wake event. the event occurs when the pme# signal goes from high to low. no event is caused when it goes from low to high. 5.12.10.4 agpbusy# (82801BAm ich2-m) table 5-47. transitions due to ri# signal present state event ri_en event s0 ri# active x ignored s1 ? s5 ri# active 0 1 ignored wake event the agpbusy# signal is an input from the agp graphics component to indicate if it is busy. if p rior to going to the c3 state the agpbusy# signal is active, then the bm_sts bit will be set. if after going to the c3 state, the agpbusy# signal goes back active, the ich2-m will treat this as if one of the pci req# signals went active. this will be treated as a break event. 82801BA ich2 and 82801BAm ich2-m datasheet 5-89 functional description 5.12.11 alt access mode before entering a low power state, several registers from powered down parts may need to be saved. in the majority of cases, this is not an issue, as registers have read and write paths. however, several of the isa compatible registers are either read only or write only. to get data out of write- only registers and to restore data into read-only registers, the ich2 implements an alternate access mode. 5.12.11.1 write only registers with read paths in alternate access mode the registers described in the following table have read paths in alternate access mode. the access number field in the table indicates which register will be returned per access to that port. table 5-48. write only registers with read paths in alternate access mode restore data restore data i/o addr # of rds access data i/o addr # of rds access data 00h 2 1 dma chan 0 base address low byte 40h 7 1 timer counter 0 status, bits [5:0] 2 dma chan 0 base address high byte 2 timer counter 0 base count low byte 01h 2 1 dma chan 0 base count low byte 3 timer counter 0 base count high byte 2 dma chan 0 base count high byte 4 timer counter 1 base count low byte 02h 2 1 dma chan 1 base address low byte 5 timer counter 1 base count high byte 2 dma chan 1 base address high byte 6 timer counter 2 base count low byte 03h 2 1 dma chan 1 base count low byte 7 timer counter 2 base count high byte 2 dma chan 1 base count high byte 41h 1 timer counter 1 status, bits [5:0] 04h 2 1 dma chan 2 base address low byte 42h 1 timer counter 2 status, bits [5:0] 2 dma chan 2 base address high byte 70h 1 bit 7 = nmi enable, bits [6:0] = rtc address 05h 2 1 dma chan 2 base count low byte c4h 2 1 dma chan 5 base address low byte 2 dma chan 2 base count high byte 2 dma chan 5 base address high byte 06h 2 1 dma chan 3 base address low byte c6h 2 1 dma chan 5 base count low byte 2 dma chan 3 base address high byte 2 dma chan 5 base count high byte 07h 2 1 dma chan 3 base count low byte c8h 2 1 dma chan 6 base address low byte 2 dma chan 3 base count high byte 2 dma chan 6 base address high byte functional description 5-90 82801BA ich2 and 82801BAm ich2-m datasheet note: 1. the ocw1 register must be read before entering alternate access mode. 2. bits 5, 3, 1, and 0 return 0. 08h 6 1 dma chan 0 ? 3 command 2 cah 2 1 dma chan 6 base count low byte 2 dma chan 0 ? 3 request 2 dma chan 6 base count high byte 3 dma chan 0 mode: bits(1:0) = ?00? cch 2 1 dma chan 7 base address low byte 4 dma chan 1 mode: bits(1:0) = ?01? 2 dma chan 7 base address high byte 5 dma chan 2 mode: bits(1:0) = ?10? ceh 2 1 dma chan 7 base count low byte 6 dma chan 3 mode: bits(1:0) = ?11?. 2 dma chan 7 base count high byte 20h 12 1 pic icw2 of master controller d0h 6 1 dma chan 4 ? 7 command 2 2 pic icw3 of master controller 2 dma chan 4 ? 7 request 3 pic icw4 of master controller 3 dma chan 4 mode: bits(1:0) = ?00? 4 pic ocw1 of master controller 1 4 dma chan 5 mode: bits(1:0) = ?01? 5 pic ocw2 of master controller 5 dma chan 6 mode: bits(1:0) = ?10? 6 pic ocw3 of master controller 6 dma chan 7 mode: bits(1:0) = ?11?. 7 pic icw2 of slave controller 8 pic icw3 of slave controller 9 pic icw4 of slave controller 10 pic ocw1 of slave controller 1 11 pic ocw2 of slave controller 12 pic ocw3 of slave controller table 5-48. write only registers with read paths in alternate access mode (continued) restore data restore data i/o addr # of rds access data i/o addr # of rds access data 82801BA ich2 and 82801BAm ich2-m datasheet 5-91 functional description 5.12.11.2 pic reserved bits many bits within the pic are reserved, and must have certain values written for the pic to operate properly. therefore, there is no need to return these values in alternate access mode. when reading pic registers from 20h and a0h, the reserved bits shall return the values listed in table 5-49 . 5.12.11.3 read only registers with write paths in alternate access mode the registers described in table 5-50 have write paths alternate access mode. software restores these values after returning from a powered down state. these registers must be handled specially by software. when in normal mode, writing to the base address and count register also writes to the current address and count register. therefore, the base address and count must be written first, then the part is put into alternate access mode and the current address and count register is written. 5.12.12 system power supplies, planes, and signals power plane control with slp_s3# and slp_s5# the slp_s3# output signal can be used to cut power to the system core supply, since it will only go active for the str state (typically mapped to acpi s3). power must be maintained to the ich2 resume well, and to any other circuits that need to generate wake signals from the str state. cutting power to the core may be done via the power supply, or by external fets to the motherboard. the slp_s5# output signal can be used to cut power to the system core supply, as well as power to the system memory, since the context of the system is saved on the disk. cutting power to the memory may be done via the power supply, or by external fets to the motherboard. table 5-49. pic reserved bits return values pic reserved bits value returned icw2(2:0) 000 icw4(7:5) 000 icw4(3:2) 00 icw4(0) 0 ocw2(4:3) 00 ocw3(7) 0 ocw3(5) reflects bit 6 ocw3(4:3) 01 table 5-50. register write accesses in alternate access mode i/o address register write value 08h dma status register for channels 0?3. d0h dma status register for channels 4?7. slp_s1# signal (82801BAm ich2-m) for the ich2-m, the slp_s1# output signal will typically be connected to the clock synthesizer?s pwrdwn# input to stop the clock synthesizer?s pll. alternative implementations may use this signal to cut power to non-critical subsystems while in the s1 state. functional description 5-92 82801BA ich2 and 82801BAm ich2-m datasheet pwrok signal the pwrok input should go active based on the core supply voltages becoming valid. pwrok should go active no sooner than 10 ms after vcc3_3 and vcc1_8 have reached their nominal values. note: traditional designs have a reset button logically and?d with the pwrok signal from the power supply and the processor?s voltage regulator module. if this is done with the ich2, the pwrok_flr bit will be set. the ich2 treats this internally as if the rsmrst# signal had gone active. however, it is not treated as a full power failure. if pwrok goes inactive and then active (but rsmrst# stays high), the ich2 reboots (regardless of the state of the afterg3 bit). if the rsmrst# signal also goes low before pwrok goes high, this is a full power failure and the reboot policy is controlled by the afterg3 bit. vrmpwrgd signal this signal is connected to the processor?s vrm and is internally and?d with the pwrok signal that comes from the system power supply. this is needed for intel ? speedstep tm technology support in mobile systems (ich2-m 82801BAm) and saves the external and gate found in desktop systems (82801BA ich2). controlling leakage and power consumption during low-power states to control leakage in the system, various signals will tri-state or go low during some low-power states. general principles ? all signals going to powered down planes (either internally or externally) must be either tri- stated or driven low. ? signals with pull-up resistors should not be low during low-power states. this is to avoid the power consumed in the pull-up resistor. ? buses should be halted (and held) in a known state to avoid a floating input (perhaps to some other device). floating inputs can cause extra power consumption. based on the above principles, the following measures are taken: ? during c2 or s3 state (c2, s3, or c3 state for ich2-m), the processor signals that have pull- ups will be tri-stated or driven low. ? during s3 (str), all signals attached to powered down planes will be tri-stated or driven low. batlow#?battery low (82801BAm ich2-m) for the ich2-m, the batlow# input can inhibit waking from a sleep state if there is not sufficient power. it will also cause an smi#, if the system is already in an s0 state. 82801BA ich2 and 82801BAm ich2-m datasheet 5-93 functional description 5.12.13 clock generators the clock generator is expected to provide the frequencies shown in table 5-51 . 5.12.13.1 clock control signals from ich2-m to clock synthesizer (82801BAm ich2-m only) table 5-51. ich2 clock inputs clock domain frequency source usage clk66 66 mhz main clock generator should be running in all cx states. stopped in s3 ~ s5 based on slp_s3# assertion. 82801BAm ich2-m: it is also stopped in the s1 state based on the assertion of slp_s1# assertion. pciclk 33 mhz main clock generator free-running pci clock to ich2. stopped in s3 ~ s5 based on slp_s3# assertion. 82801BAm ich2-m: free-running (not affected by stp_pci#) pci clock to ich2-m. this is not the system pci clock. this clock must keep running in s0 while the system pci clock may stop based on clkrun# protocol . this clock is stopped in s1 based on slp_s1# assertion. stopped in s3 ~ s5 based on slp_s3# assertion. clk48 48 mhz main clock generator used by usb controllers. stopped in s3 ~ s5 based on slp_s3# assertion. 82801BAm ich2-m: this clock is also stopped in s1 based on slp_s1# assertion. clk14 14.318 mhz main clock generator used by acpi timers. stopped in s3 ~ s5 based on slp_s3# assertion. 82801BAm ich2-m: this clock is also stopped in s1 based on slp_s1# assertion. ac_bit_clk 12.288 mhz ac?97 codec ac?97 link. control policy is determined by the clock source. apicclk 16.67 mhz or 33 mhz main clock generator used for ich2-processor interrupt messages. should be running in c0, c1 and c2. stopped in s3 ~ s5 based on slp_s3# assertion. 82801BAm ich2-m: also stopped in c3 based on stp_cpu# assertion. stopped in s1 based on slp_s1# assertion. lan_clk 0.8 to 50 mhz lan connect lan connect link. control policy is determined by the clock source. the clock generator is assumed to have direct connect from the following ich2-m signals: ? stp_cpu# stops cpu clocks in c3 state ? stp_pci# stops system pci clocks (not the ich2-m free-running 33 mhz clock) due to clkrun# protocol ? slp_s1# stops all clocks in s1 functional description 5-94 82801BA ich2 and 82801BAm ich2-m datasheet 5.12.14 legacy power management theory of operation instead of relying on acpi software, legacy power management uses bios and various hardware mechanisms. ich2 has a greatly simplified method for legacy power management compared with previous generations (e.g., piix4). the scheme relies on the concept of detecting when individual subsystems are idle, detecting when the whole system is idle, and detecting when accesses are attempted to idle subsystems. however, the operating system is assumed to be at least apm enabled. without apm calls, there is no quick way to know when the system is idle between keystrokes. the ich2 does not support the burst modes found in previous components (e.g., piix4). 5.12.14.1 desktop apm power management (82801BA ich2 only) 5.12.14.2 mobile apm power management (82801BAm ich2-m only) the ich2 has a timer that, when enabled by the 1min_en bit in the smi control and enable register, generates an smi# once per minute. the smi handler can check for system activity by reading the devact_sts register. if none of the system bits are set, the smi handler can increment a software counter. when the counter reaches a sufficient number of consecutive minutes with no activity, the smi handler can then put the system into a lower power state. if there is activity, various bits in the devact_sts register are set. software clears the bits by writing a 1 to the bit position. the devact_sts register allows for monitoring various internal devices, or super i/o devices (sp, pp, fdc) on lpc or pci, keyboard controller accesses, or audio functions on lpc or pci. other pci activity can be monitored by checking the pci interrupts. in mobile systems, there are additional requirements associated with device power management. to handle this, the ich2-m has specific smi# traps available. the following algorithm is used: 1. the periodic smi# timer checks if a device is idle for the require time. if so, it puts to the device into a low-power states and sets the associated smi# trap. 2. when software (not the smi# handler) attempts to access the device, a trap occurs (the cycle doesn?t really go to the device and an smi# is generated). 3. the smi# handler turns on the device and turns off the trap the smi# handler exits with an i/o restart. this allows the original software to continue. 82801BA ich2 and 82801BAm ich2-m datasheet 5-95 functional description 5.13 system management (d31:f0) the ich2 provides various functions to make a system easier to manage and to lower the total cost of ownership (tco) of the system. features and functions can be augmented via external a/d converters and gpio, as well as an external microcontroller. the following features and functions are supported by the ich2: ? processor present detection. ? detects if processor fails to fetch the first instruction after reset. ? various error detection (e.g., ecc errors) indicated by host controller ? can generate smi#, sci, serr, nmi, or tco interrupt ? intruder detect input ? can generate tco interrupt or smi# when the system cover is removed. ? intruder# allowed to go active in any power state, including g3. ? detection of bad fwh programming ? detects if data on first read is ffh (indicates unprogrammed fwh) note: voltage id from the processor can be read via gpi signals. 5.13.1 theory of operation the system management functions are designed to allow the system to diagnose failing subsystems. the intent of this logic is that some of the system management functionality be provided without the aid of an external microcontroller. detecting a system lockup when the processor is reset, it is expected to fetch its first instruction. if the processor fails to fetch the first instruction after reset, the tco timer times out twice and the ich2 asserts pcirst#. handling an intruder the ich2 has an input signal (intruder#) that can be attached to a switch that is activated by the system?s case being open. this input has a 2 rtc clock debounce. if intruder# goes active (after the debouncer), this will set the intrd_det bit in the tco_sts register. the intrd_sel bits in the tco_cnt register can enable the ich2 to cause an smi# or interrupt. the bios or interrupt handler can then cause a transition to the s5 state by writing to the slp_en bit. the software can also directly read the status of the intruder# signal (high or low) by clearing and then reading the intrd_det bit. this allows the signal to be used as a gpi if the intruder function is not required. note: the intrd_det bit resides in the ich2?s rtc well, and is set and cleared synchronously with the rtc clock. thus, when software attempts to clear intrd_det (by writing a ?1? to the bit location) there may be as much as 2 rtc clocks (about 65 s) delay before the bit is actually cleared. also, the intruder# signal should be asserted for a minimum of 1 ms to guarantee that the intrd_det bit will be set. note: if the intruder# signal is still active when software attempts to clear the intrd_det bit, the bit will remain set and the smi will be generated again immediately. the smi handler can clear the intrd_sel bits to avoid further smis. however, if the intruder# signal goes inactive and then active again, there will not be further smis, since the intrd_sel bits would select that no smi# be generated. functional description 5-96 82801BA ich2 and 82801BAm ich2-m datasheet detecting improper fwh programming the ich2 can detect the case where the fwh is not programmed. this results in the first instruction fetched to have a value of ffh. if this occurs, the ich2 sets the bad_bios bit, which can then be reported via the heartbeat and event reporting using an external, alert on lan* enabled lan controller (see section 5.13.2 ). handling an ecc error or other memory error the host controller provides a message to indicate that it would like to cause an smi#, sci, serr#, or nmi. the software must check the host controller as to the exact cause of the error. 5.13.2 alert on lan* the ich2 integrated lan controller supports alert on lan* functionality when used with the 82562em platform lan connect component. this allows the integrated lan controller to report messages to a network management console without the aid of the system processor. this is crucial in cases where the processor is malfunctioning or cannot function due to being in a low-power state. the ich2 also features an independent, dedicated smbus interface, referred to as the smlink interface that can be used with an external alert on lan* (or alert on lan 2*) enabled lan controller. this separate interface is required, since devices on the system smbus will be powered down during some low power states. the basic scheme is for the ich2 integrated lan controller to send a prepared ethernet message to a network management console. the prepared message is stored in the non-volatile eeprom that is connected to the ich2. messages are sent by the lan controller either because a specific event has occurred or they are sent periodically (also known as a heartbeat). the event and heartbeat messages have the exact same format. the event messages are sent based on events occurring. the heartbeat messages are sent every 30 to 32 seconds. when an event occurs, the ich2 sends a new message and increments the seq[3:0] field. for heartbeat messages, the sequence number does not increment. if the policy is for the ich2 to reboot the system after a hardware lockup, the ich2 does not immediately send an alert on lan* message. it first attempts to reboot the processor and let the bios perform the appropriate recovery (and potentially send the message). however, if the boot fails, the ich2 sends the message. if the policy is for the ich2 not to reboot after a hardware lockup, the ich2 sends an alert on lan* message with the watchdog (wd) event status bit set. this message is sent as soon as the lockup is detected. the message is sent with the next incremented sequence number. if a system is locked, the ich2 continues sending the alert on lan* messages every heartbeat period (30?32 seconds) unless one of the following occurs: ? the system is suspended via a powerbutton override. ? the no_reboot bit (d31:f0, offset d4h, bit 1) is set and the system is reset using pwrok, or the system is reset remotely by smlink smbus slave write and bios clears the second_to_sts bit before a tco timeout can occur. ? the no_reboot bit (d31:f0, offset d4h, bit 1) is not set causing the system to reboot automatically. if another event occurs prior to a power button override, the ich2 will send another alert on lan* message with the next incremented sequence number and appropriate status bit set. 82801BA ich2 and 82801BAm ich2-m datasheet 5-97 functional description if a boot is unsuccessful (processor does not fetch the first instruction), then the ich2 will send an alert on lan* message with the processor event status bit set and the next incremented sequence number. this message will be sent as soon as the lockup is detected (2 tco timer time-outs). if the system is in a g1 (s1?s4) state the ich2 will send a heartbeat message every 30?32 seconds. if an event occurs prior to the system being shutdown, the ich2 immediately sends an event message with the next incremented sequence number. after the event message, the ich2 resumes sending heartbeat messages. note: normally, the ich2 does not send heartbeat messages while in the g0 state (except in the case of a lockup). however, if a hardware event (or heartbeat) occurs just as the system is transitioning into a g0 state, the hardware continues to send the message even though the system is in a g0 state (and the status bits may indicate this). when used with an external alert on lan* enabled lan controller, the ich2 sends these messages via the smlink signals. when sending messages via these signals, the ich2 abides by the smbus rules associated with collision detection. it delays starting a message until the bus is idle and detects collisions. if a collision is detected, the ich2 waits until the bus is idle and tries again. table 5-52 shows the data included in the alert on lan* messages. table 5-52. alert on lan* message data field comment cover tamper status 1 = this bit will be set if the intruder detect bit is set (intrd_det). temp event status 1 = this bit will be set if the ich2therm# input signal is asserted. processor missing event status 1 = this bit will be set if the processor failed to fetch the first instruction. tco timer event status 1 = this bit is set when the tco timer expires. software event status 1 = this bit is set when software writes a 1 to the send_now bit. unprogrammed fwh event status 1 = first bios fetch returned a value of ffh, indicating that the fwh has not yet been programmed (still erased). gpio status 1 = this bit is set when gpio[11] signal is high. 0 = this bit is cleared when gpio[11] signal is low. seq[3:0] this is a sequence number. it will initially be 0, and will increment each time the ich2 sends a new message. upon reaching 1111, t hen the sequence number will roll over to 0000. msb (seq3) sent first. system power state 00 = g0, 01 = g1, 10 = g2, 11 = pre-boot. msb sent first message1 same as the message1 register. msb sent first. message2 same as the message2 register. msb sent first. wdstatus same as the wdstatus register. msb sent first. functional description 5-98 82801BA ich2 and 82801BAm ich2-m datasheet 5.14 general purpose i/o power wells some gpios exist in the resume power plane. care must be taken to make sure gpio signals are not driven high into powered-down planes. some ich2 gpios may be connected to pins on devices that exist in the core well. if these gpios are outputs, there is a danger that a loss of core power (pwrok low) or a power button override event will result in the ich2 driving a pin to a logic 1 to another device that is powered down. smi# and sci routing the routing bits for gpio[13:11,8:6,4:3,1:0] (gpio[13:11,8:7,4:3,1:0] for the ich2-m) allow an input to be routed to smi# or sci, or neither. note that a bit can be routed to either an smi# or an sci, but not both. power wells gpio[13:11,8:6,4:3,1] (gpio[13:11,8:7,4:3,1:0] for the ich2-m) have "sticky" bits on the input. refer to the gpe1_sts register. as long as the signal goes active for at least 2 clocks, the ich2 will keep the sticky status bit active. the active level can be selected in the gp_lvl register. if the input signal is still active when the latch is cleared, it will again be set. another edge trigger is not required. this makes these signals "level" triggered inputs. for the 82801BA ich2, if the system is in an s0 or an s1 state, the gpi inputs are sampled at 33 mhz, so the signal only needs to be active for about 60 ns to be latched. in the s3?s5 states, the gpi inputs are sampled at 32.768 khz, and thus must be active for at least 61 microseconds to b e latched. for the 82801BAm ich2-m, if the system is in an s0 state, the gpi inputs are sampled at 33 mhz, so the signal only needs to be active for about 60 ns to be latched. in the s1 or s3?s5 states, the gpi inputs are sampled at 32.768 khz, and thus must be active for at least 61 microseconds to be latched. 82801BA ich2 and 82801BAm ich2-m datasheet 5-99 functional description 5.15 ide controller (d31:f1) the ich2 ide controller features two sets of interface signals (primary and secondary) that can be independently enabled, tri-stated or driven low. the ide interfaces of the ich2 can support several types of data transfers: ? programmed i/o (pio): processor is in control of the data transfer. ? 8237 style dma: dma protocol that resembles the dma on the isa bus, although it does not use the 8237 in the ich2. this protocol off loads the processor from moving data. this allows higher transfer rate of up to 16 mb/s. ? ultra ata/33: dma protocol that redefines signals on the ide cable to allow both host and target throttling of data and transfer rates of up to 33 mb/s. ? ultra ata/66: dma protocol that redefines signals on the ide cable to allow both host and target throttling of data and transfer rates of up to 66 mb/s. ? ultra ata/100: dma protocol that redefines signals on the ide cable to allow both host and target throttling of data and transfer rates of up to 100 mb/s. 5.15.1 pio transfers the ich2 ide controller includes both compatible and fast timing modes. the fast timing modes can be enabled only for the ide data ports. all other transactions to the ide registers are run in single transaction mode with compatible timings. up to 2 ide devices may be attached per ide connector (drive 0 and drive 1). the idetim and sidetim registers permit different timing modes to be programmed for drive 0 and drive 1 of the same connector. the ultra ata/33/66/100 synchronous dma timing modes can also be applied to each drive by programming the ide i/o configuration register and the synchronous dma control and timing registers. when a drive is enabled for synchronous dma mode operation, the dma transfers are executed with the synchronous dma timings. the pio transfers are executed using compatible timings or fast timings if also enabled. pio ide timing modes ide data port transaction latency consists of startup latency, cycle latency, and shutdown latency: ? startup latency is incurred when a pci master cycle targeting the ide data port is decoded and the da[2:0] and csxx# lines are not set up. startup latency provides the setup time for the da[2:0] and csxx# lines prior to assertion of the read and write strobes (dior# and diow#). ? cycle latency consists of the i/o command strobe assertion length and recovery time. recovery time is provided so that transactions may occur back-to-back on the ide interface (without incurring startup and shutdown latency) without violating minimum cycle periods for the ide interface. the command strobe assertion width for the enhanced timing mode is selected by the idetim register and may be set to 2, 3, 4, or 5 pci clocks. the recovery time is selected by the idetim register and may be set to 1, 2, 3, or 4 pci clocks. if iordy is asserted when the initial sample point is reached, no wait states are added to the command strobe assertion length. if iordy is negated when the initial sample point is reached, additional wait states are added. since the rising edge of iordy must be synchronized, at least two additional pci clocks are added. functional description 5-100 82801BA ich2 and 82801BAm ich2-m datasheet ? shutdown latency is incurred after outstanding scheduled ide data port transactions (either a non-empty write post buffer or an outstanding read prefetch cycles) have completed and before other transactions can proceed. it provides hold time on the da[2:0] and csxx# lines with respect to the read and write strobes (dior# and diow#). shutdown latency is 2 pci clocks in duration. the ide timings for various transaction types are shown in table 5-53 . note that bit 2 (16 bit i/o recovery enable) of the isa i/o recovery timer register does not add wait states to ide data port read accesses when any of the fast timing modes are enabled. iordy masking the iordy signal can be ignored and assumed asserted at the first iordy sample point (isp) on a drive by drive basis via the idetim register. pio 32 bit ide data port accesses a 32-bit pci transaction run to the ide data address (01f0h primary, 0170h secondary) results in two back-to-back 16-bit transactions to the ide data port. the 32-bit data port feature is enabled for all timings, not just enhanced timing. for compatible timings, a shutdown and startup latency is incurred between the two 16-bit halves of the ide transaction. this guarantees that the chip selects will be deasserted for at least 2 pci clocks between the 2 cycles. pio ide data port prefetching and posting the ich2 can be programmed via the idetim registers to allow data to be posted to and prefetched from the ide data ports. data prefetching is initiated when a data port read occurs. the read prefetch eliminates latency to the ide data ports and allows them to be performed back to back for the highest possible pio data transfer rates. the first data port read of a sector is called the demand read. subsequent data port reads from the sector are called prefetch reads. the demand read and all prefetch reads much be of the same size (16 or 32 bits). data posting is performed for writes to the ide data ports. the transaction is completed on the pci bus after the data is received by the ich2. the ich2 then runs the ide cycle to transfer the data to the drive. if the ich2 write buffer is non-empty and an unrelated (non-data or opposite channel) ide transaction occurs, that transaction is stalled until all current data in the write buffer is transferred to the drive. table 5-53. ide transaction timings (pci clocks) ide transaction type startup latency iordy sample point (isp) recovery time (rct) shutdown latency non-data port compatible 4 11 22 2 data port compatible 3 6 14 2 fast timing mode 2 2 ? 51 ? 42 82801BA ich2 and 82801BAm ich2-m datasheet 5-101 functional description 5.15.2 bus master function the ich2 can act as a pci bus master on behalf of an ide slave device. two pci bus master channels are provided, one channel for each ide connector (primary and secondary). by performing the ide data transfer as a pci bus master, the ich2 off-loads the processor and improves system performance in multitasking environments. both devices attached to a connector can be programmed for bus master transfers, but only one device per connector can be active at a time. physical region descriptor format the physical memory region to be transferred is described by a physical region descriptor (prd). the prds are stored sequentially in a descriptor table in memory. the data transfer proceeds until all regions described by the prds in the table have been transferred. note that the ich2 bus master ide function does not support memory regions or descriptor tables located on isa. descriptor tables must be aligned on 64 kb boundaries. each prd entry in the table is 8 bytes in length. the first 4 bytes specify the byte address of a physical memory region. this memory region must be dword aligned and must not cross a 64 kb boundary. the next two bytes specify the size or transfer count of the region in bytes (64 kb limit per region). a value of zero in these two bytes indicates 64 kb (thus the minimum transfer count is 1). if bit 7 (eot) of the last byte is a 1, it indicates that this is the final prd in the descriptor table. bus master operation terminates when the last descriptor has been retired. when the bus master ide controller is reading data from the memory regions, bit 1 of the base address is masked and byte enables are asserted for all read transfers. when writing data, bit 1 of the base address is not masked and if set, causes the lower word byte enables to be deasserted for the first dword transfer. the write to pci typically consists of a 32-byte cache line. if valid data ends prior to end of the cache line, the byte enables will be deasserted for invalid data. the total sum of the byte counts in every prd of the descriptor table must be equal to or greater than the size of the disk transfer request. if greater than the disk transfer request, the driver must terminate the bus master transaction (by setting bit 0 in the bus master ide command register to 0) when the drive issues an interrupt to signal transfer completion. figure 5-15. physical region descriptor table entry byte 3 byte 2 byte 1 byte 0 memory region physical base address [31:1] byte count [15:1] reserved eot 0 0 main memory main region functional description 5-102 82801BA ich2 and 82801BAm ich2-m datasheet line buffer a single line buffer exists for the ich2 bus master ide interface. this buffer is not shared with any other function. the buffer is maintained in either the read state or the write state. memory writes are typically 4-dword bursts and invalid dwords have c/be[3:0]#=0fh. the line buffer allows burst data transfers to proceed at peak transfer rates. the bus master ide active bit in bus master ide status register is reset automatically when the controller has transferred all data associated with a descriptor table (as determined by eot bit in last prd). the ide interrupt status bit is set when the ide device generates an interrupt. these events may occur prior to line buffer emptying for memory writes. if either of these conditions exist, all pci master non-memory read accesses to ich2 are retried until all data in the line buffers has been transferred to memory. bus master ide timings the timing modes used for bus master ide transfers are identical to those for pio transfers. the dma timing enable only bits in ide timing register can be used to program fast timing mode for dma transactions only. this is useful for ide devices whose dma transfer timings are faster that its pio transfer timings. the ide device dma request signal is sampled on the same pci clock that dior# or diow# is deasserted. if inactive, the dma acknowledge signal is deasserted on the next pci clock and no more transfers take place until dma request is asserted again. interrupts the ich2 is connected to irq14 for the primary interrupt and irq15 for the secondary interrupt. this connection is done from the isa pin, before any mask registers. this implies the following: ? bus master ide is operating under an interrupt based driver. therefore, it does not operate under environments where the ide device drives an interrupt but the interrupt is masked in the system. ? bus master ide devices are connected directly off of ich2. ide interrupts cannot be communicated through pci devices or the serial stream. bus master ide operation to initiate a bus master transfer between memory and an ide device, the following steps are required: 1. software prepares a prd table in system memory. the prd table must be dword aligned and must not cross a 64 kb boundary. 2. software provides the starting address of the prd table by loading the prd table pointer register. the direction of the data transfer is specified by setting the read/write control bit. the interrupt bit and error bit in the status register are cleared. 3. software issues the appropriate dma transfer command to the disk device. 4. the bus master function is engaged by software writing a '1' to the start bit in the command register. the first entry in the prd table is fetched and loaded into two registers which are not visible by software, the current base and current count registers. these registers hold the current value of the address and byte count loaded from the prd table. the value in these registers is only valid when there is an active command to an ide device. 5. once the prd is loaded internally, the ide device will receive a dma acknowledge. 82801BA ich2 and 82801BAm ich2-m datasheet 5-103 functional description 6. the controller transfers data to/from memory responding to dma requests from the ide device. the ide device and the host controller may or may not throttle the transfer several times. when the last data transfer for a region has been completed on the ide interface, the next descriptor is fetched from the table. the descriptor contents are loaded into the current base and current count registers. 7. at the end of the transfer the ide device signals an interrupt. 8. in response to the interrupt, software resets the start/stop bit in the command register. it then reads the controller status followed by the drive status to determine if the transfer completed successfully. the last prd in a table has the end of list (eol) bit set. the pci bus master data transfers terminate when the physical region described by the last prd in the table has been completely transferred. the active bit in the status register is reset and the ddrq signal masked. the buffer is flushed (when in the write state) or invalidated (when in the read state) when a terminal count condition exists (i.e., the current region descriptor has the eol bit set and that region has been exhausted). the buffer is also flushed (write state) or invalidated (read state) when the interrupt bit in the bus master ide status register is set. software that reads the status register and finds the error bit reset, and either the active bit reset or the interrupt bit set, can be assured that all data destined for system memory has been transferred and that data is valid in system memory. table 5-54 describes how to interpret the interrupt and active bits in the status register after a dma transfer has started. during concurrent dma or ultra ata transfers, the ich2 ide interface arbitrates between the primary and secondary ide cables when a prd expires. table 5-54. interrupt/active bit interaction definition interrupt active description 0 1 dma transfer is in progress. no interrupt has been generated by the ide device. 10 the ide device generated an interrupt. the controller exhausted the physical region descriptors. this is the normal completion case where the size of the physical memory regions was equal to the ide device transfer size. 11 the ide device generated an interrupt. the controller has not reached the end of the physical memory regions. this is a valid completion case where the size of the physical memory regions was larger than the ide device transfer size. 00 this bit combination signals an error condition. if the error bit in the status register is set, then the controller has some problem transferring data to/from memory. specifics of the error have to be determined using bus-specific information. if the error bit is not set, then the prd's specified a smaller size than the ide transfer size. functional description 5-104 82801BA ich2 and 82801BAm ich2-m datasheet error conditions ide devices are sector based mass storage devices. the drivers handle errors on a sector basis; either a sector is transferred successfully or it is not. a sector is 512 bytes. if the ide device does not complete the transfer due to a hardware or software error, the command will eventually be stopped by the driver setting command start bit to zero when the driver times out the disk transaction. information in the ide device registers help isolate the cause of the problem. if the controller encounters an error while doing the bus master transfers it stops the transfer (i.e., reset the active bit in the command register) and sets the error bit in the bus master ide status register. the controller does not generate an interrupt when this happens. the device driver can use device specific information (pci configuration space status register and ide drive register) to determine what caused the error. when a requested transfer does not complete properly, information in the ide device registers (sector count) can be used to determine how much of the transfer was completed and to construct a new prd table to complete the requested operation. in most cases the existing prd table can be used to complete the operation. 8237-like protocol the 8237 mode dma is similar in form to dma used on the isa bus. this mode uses pins familiar to the isa bus, namely a dma request, a dma acknowledge, and i/o read/write strobes. these pins have similar characteristics to their isa counterparts in terms of when data is valid relative to strobe edges, and the polarity of the strobes, however the ich2 does not use the 8237 for this mode. 82801BA ich2 and 82801BAm ich2-m datasheet 5-105 functional description 5.15.3 ultra ata/33 protocol ultra ata/33 is enabled through configuration register 48h in device 31:function 1 for each ide device. the ide signal protocols are significantly different under this mode than for the 8237 mode. ultra ata/33 is a physical protocol used to transfer data between a ultra ata/33 capable ide controller such as the ich2 and one or more ultra ata/33 capable ide devices. it utilizes the standard bus master ide functionality and interface to initiate and control the transfer. ultra ata/33 utilizes a ?source synchronous? signaling protocol to transfer data at rates up to 33 mb/s. the ultra ata/33 definition also incorporates a cyclic redundancy checking (crc-16) error checking protocol. signal descriptions the ultra ata/33 protocol requires no extra signal pins on the ide connector. it does redefine a number of the standard ide control signals when in ultra ata/33 mode. these redefinitions are shown in table 5-55 . read cycles are defined as transferring data from the ide device to the ich2. write cycles are defined as transferring data from ich2 to ide device. the diow# signal is redefined as stop for both read and write transfers. this is always driven by the ich2 and is used to request that a transfer be stopped or as an acknowledgment to stop a request from the ide device. the dior# signal is redefined as dmardy# for transferring data from the ide device to the ich2 (read). it is used by the ich2 to signal when it is ready to transfer data and to add wait states to the current transaction. the dior# signal is redefined as strobe for transferring data from the ich2 to the ide device (write). it is the data strobe signal driven by the ich2 on which data is transferred during each rising and falling edge transition. the iordy signal is redefined as strobe for transferring data from the ide device to the ich2 (read). it is the data strobe signal driven by the ide device on which data is transferred during each rising and falling edge transition. the iordy signal is redefined as dmardy# for transferring data from the ich2 to the ide device (write). it is used by the ide device to signal when it is ready to transfer data and to add wait states to the current transaction. all other signals on the ide connector retain their functional definitions during ultra ata/33 operation. table 5-55. ultraata/33 control signal redefinitions standard ide signal definition ultra ata/33 read cycle definition ultra ata/33 write cycle definition ich2 primary channel signal ich2 secondary channel signal diow# stop stop pdiow# sdiow# dior# dmardy# strobe pdior# sdior# iordy strobe dmardy# piordy siordy functional description 5-106 82801BA ich2 and 82801BAm ich2-m datasheet operation initial setup programming consists of enabling and performing the proper configuration of ich2 and the ide device for ultra ata/33 operation. for ich2, this consists of enabling synchronous dma mode and setting up appropriate synchronous dma timings. when ready to transfer data to or from an ide device, the bus master ide programming model is followed. once programmed, the drive and ich2 control the transfer of data via the ultra ata/33 protocol. the actual data transfer consists of three phases, a start-up phase, a data transfer phase, and a burst termination phase. the ide device begins the start-up phase by asserting dmarq signal. when ready to begin the transfer, the ich2 asserts the dmack# signal. when dmack# signal is asserted, the host controller drives cs0# and cs1# inactive, da0?da2 low. for write cycles, the ich2 deasserts stop, waits for the ide device to assert dmardy#, and then drives the first data word and strobe signal. for read cycles, the ich2 tri-states the dd lines, deasserts stop, and asserts dmardy#. the ide device then sends the first data word and strobe. the data transfer phase continues the burst transfers with the data transmitter (ich2 - writes, ide device - reads) providing data and toggling strobe. data is transferred (latched by receiver) on each rising and falling edge of strobe. the transmitter can pause the burst by holding strobe high or low, resuming the burst by again toggling strobe. the receiver can pause the burst by deasserting dmardy# and resumes the transfers by asserting dmardy#. the ich2 pauses a burst transaction to prevent an internal line buffer over or under flow condition, resuming once the condition has cleared. it may also pause a transaction if the current prd byte count has expired, resuming once it has fetched the next prd. the current burst can be terminated by either the transmitter or receiver. a burst termination consists of a stop request, stop acknowledge and transfer of crc data. the ich2 can stop a burst by asserting stop; the ide device acknowledges by deasserting dmarq. the ide device stops a burst by deasserting dmarq and the ich2 acknowledges by asserting stop. the transmitter then drives the strobe signal to a high level. the ich2 then drives the crc value on the dd lines and deasserts dmack#. the ide device latches the crc value on the rising edge of dmack#. the ich2 terminates a burst transfer if it needs to service the opposite ide channel, if a programmed i/o (pio) cycle is executed to the ide channel currently running the burst, or upon transferring the last data from the final prd. crc calculation cyclic redundancy checking (crc-16) is used for error checking on ultra ata/33 transfers. the crc value is calculated for all data by both the ich2 and the ide device over the duration of the ultra ata/33 burst transfer segment. this segment is defined as all data transferred with a valid strobe edge from ddack# assertion to ddack# deassertion. at the end of the transfer burst segment, the ich2 drives the crc value onto the dd[15:0] signals. it is then latched by the ide device on deassertion of ddack#. the ide device compares the ich2 crc value to its own and reports an error if there is a mismatch. 82801BA ich2 and 82801BAm ich2-m datasheet 5-107 functional description 5.15.4 ultra ata/66 protocol in addition to ultra ata/33, the ich2 supports the ultra ata/66 protocol. the ultra ata/66 protocol is enabled via configuration bits 3:0 at offset 54h. the two protocols are similar, and are intended to be device driver compatible. the ultra ata/66 logic can achieve transfer rates of up to 66 mb/s. to achieve the higher data rate, the timings are shortened and the quality of the cable is improved to reduce reflections, noise, and inductive coupling. note that the improved cable is required and will still plug into the standard ide connector. the ultra ata/66 protocol also supports a 44 mb/s mode. 5.15.5 ultra ata/100 protocol when the ata_fast bit is set for any of the 4 ide devices, the timings for the transfers to and from the corresponding device run at a higher rate. the ich2 ultra ata/100 logic can achieve read transfer rates up to 100 mb/s and write transfer rates up to 88.9 mb/s. the cable improvements required for ultra ata/66 are sufficient for ultra ata/100, so no further cable improvements are required when implementing ultra ata/100. 5.15.6 ultra ata/33/66/100 timing the timings for ultra ata/33/66/100 modes are programmed via the synchronous dma timing register and the ide configuration register. different timings can be programmed for each drive in the system. the base clock frequency for each drive is selected in the ide configuration register. the cycle time (ct) and ready to pause (rp) time (defined as multiples of the base clock) are programmed in the synchronous dma timing register. the cycle time represents the minimum pulse width of the data strobe (strobe) signal. the ready to pause time represents the number of base clock periods that the ich2 will wait from deassertion of dmardy# to the assertion of stop when it desires to stop a burst read transaction. note: the internal base clock for ultra ata/100 (mode 5) runs at 133 mhz, and the cycle time (ct) must be set for 3 base clocks. the ich2, thus, toggles the write strobe signal every 22.5 ns, transferring two bytes of data on each strobe edge. this means that the ich2 performs mode 5 write transfers at a maximum rate of 88.9 mb/s. for read transfers, the read strobe is driven by the ata/100 device; the ich2 supports reads at the maximum rate of 100 mb/s. 5.15.7 mobile ide swap bay (82801BAm ich2-m only) to support a mobile swap bay, the ich2-m allows the ide output signals to be tri-stated and input b uffers to be turned off. this should be done prior to the removal of the drive. the output signals can also be driven low. this can be used to remove charge built up on the signals.new configuration bits are included in the ide i/o configuration register, offset 54h in the ide pci configuration space. warning: the software should not attempt to control the outputs (either tri-state or driving low), while an ide transfer is in progress. unpredictable results could occur, including a system lockup. functional description 5-108 82801BA ich2 and 82801BAm ich2-m datasheet 5.16 usb controller (device 31:functions 2 and 4) the ich2 contains two usb host controllers. each host controller includes a root hub with two separate usb ports each, for a total of 4 usb ports. the ich2 host controllers support the standard universal host controller interface (uhci) rev 1.1. overcurrent detection on all 4 usb ports is supported. the overcurrent inputs are 5v-tolerant, and can be used as gpis if not needed. the ich2?s usb controllers are arbitrated as differently than standard pci devices to improve arbitration latency. 5.16.1 data structures in main memory this section describes the details of the data structures used to communicate control, status, and data between software and the ich2: frame lists, transfer descriptors, and queue heads. frame lists are aligned on 4-kb boundaries. transfer descriptors and queue heads are aligned on 16-byte boundaries. 5.16.1.1 frame list pointer the frame list pointer contains a link pointer to the first data object to be processed in the frame, as well as the control bits defined in table 5-56 . table 5-56. frame list pointer bit description bit description 31:4 frame list pointer (flp). this field contains the address of the first data object to be processed in the frame and corresponds to memory address signals [31:4], respectively. 3:2 reserved. these bits must be written as 0. 1 qh/td select (q). this bit indicates to the hardware whether the item referenced by the link pointer is a td (transfer descriptor) or a qh (queue head). this allows the ich2 to perform the proper type of processing on the item after it is fetched. 1 = qh 0 = td 0 terminate (t). this bit indicates to the ich2 whether the schedule for this frame has valid entries in it. 1 = empty frame (pointer is invalid). 0 = pointer is valid (points to a qh or td). 82801BA ich2 and 82801BAm ich2-m datasheet 5-109 functional description 5.16.1.2 transfer descriptor (td) transfer descriptors (tds) express the characteristics of the transaction requested on usb by a client. tds are always aligned on 16-byte boundaries, and the elements of the td are shown in figure 5-16 . the 4 different usb transfer types are supported by a small number of control bits in the descriptor that the ich2 interprets during operation. all transfer descriptors have the same basic, 32-byte structure. during operation, the ich2 hardware performs consistency checks on some fields of the td. if a consistency check fails, the ich2 halts immediately and issues an interrupt to the system. this interrupt cannot be masked within the ich2. figure 5-16. transfer descriptor table 5-57. td link pointer bit description 31:4 link pointer (lp). bits [31:4] correspond to memory address signals [31:4], respectively. this field points to another td or qh. 3 reserved. must be 0 when writing this field. 2 depth/breadth select (vf). this bit is only valid for queued tds and indicates to the hardware whether it should process in a depth first or breadth first fashion. when set to depth first, it informs the ich2 to process the next transaction in the queue rather than starting a new queue. 1 = depth first. 0 = breadth first. 1 qh/td select (q). this bit informs the ich2 whether the item referenced by the link pointer is another td or a qh. this allows the ich2 to perform the proper type of processing on the item after it is fetched 1 = qh. 0 = td. 0 terminate (t). this bit informs the ich2 that the link pointer in this td does not point to another valid entry. when encountered in a queue context, this bit indicates to the ich2 that there are no more valid entries in the queue. a td encountered outside of a queue context with the t bit set informs the ich2 that this is the last td in the frame. 1 = link pointer field not valid. 0 = link pointer field is valid. tfd q 0 0 1 2 3 4 31 maxlen t 7 8 15 16 23 24 10 11 14 18 19 20 rd status r 25 26 27 28 29 30 21 ich2 read only link pointer endpt device address pid actlen vf c_err ls spd isoisc r buffer pointer r = reserved ich2 read/write functional description 5-110 82801BA ich2 and 82801BAm ich2-m datasheet table 5-58. td control and status bit description 31:30 reserved. 29 short packet detect (spd). when a packet has this bit set to 1 and the packet is an input packet, is in a queue; and successfully completes with an actual length less than the maximum length then the td is marked inactive, the queue header is not updated and the usbint status bit (status register) is set at the end of the frame. in addition, if the interrupt is enabled, the interrupt will be sent at the end of the frame. note that any error (e.g., babble or fifo error) prevents the short packet from being reported. the behavior is undefined when this bit is set with output packets or packets outside of queues. 1 = enable. 0 = disable. 28:27 error counter (c_err). this field is a 2-bit down counter that keeps track of the number of errors detected while executing this td. if this field is programmed with a non zero value during setup, the ich2 decrements the count and writes it back to the td if the transaction fails. if the counter counts from one to zero, the ich2 marks the td inactive, sets the ?stalled? and error status bit for the error that caused the transition to zero in the td. an interrupt will be generated to host controller driver (hcd) if the decrement to zero was caused by data buffer error, bit stuff error, or if enabled, a crc or timeout error. if hcd programs this field to zero during setup, the ich2 will not count errors for this td and there will be no limit on the retries of this td. bits[28:27] interrupt after 00 no error limit 01 1 error 10 2 errors 11 3 errors error decrement counter error decrement counter crc error yes data buffer error yes timeout error yes stalled no* nak received no bit stuff error yes babble detected no* *detection of babble or stall automatically deactivates the td. thus, count is not decremented. * detection of babble or stall automatically deactivates the td. thus, count is not decremented. 26 low speed device (ls). this bit indicates that the target device (usb data source or sink) is a low speed device, running at 1.5 mb/s, instead of at full speed (12 mb/sec). there are special restrictions on schedule placement for low speed tds. if an ich2 root hub port is connected to a full speed device and this bit is set to a 1 for a low speed transaction, the ich2 sends out a low speed preamble on that port before sending the pid. no preamble is sent if a ich2 root hub port is connected to a low speed device. 1 = low speed device 0 = full speed device 25 isochronous select (ios). the field specifies the type of the data structure. if this bit is set to a 1, then the td is an isochronous transfer. isochronous tds are always marked inactive by the hardware after execution, regardless of the results of the transaction. 1 = isochronous transfer descriptor 0 = non-isochronous transfer descriptor 24 interrupt on complete (ioc). this specifies that the ich2 should issue an interrupt on completion of the frame in which this transfer descriptor is executed. even if the active bit in the td is already cleared when the td is fetched (no transaction will occur on usb), an ioc interrupt is generated at the end of the frame. 1 = issue ioc 23 active. for ich2 schedule execution operations, see the data transfers to/from main memory section. 1 = set to 1 by software to enable the execution of a message transaction by the ich2. 0 = when the transaction associated with this descriptor is completed, the ich2 sets this bit to 0 indicating that the descriptor should not be executed when it is next encountered in the schedule. the active bit is also set to 0 if a stall handshake is received from the endpoint. 82801BA ich2 and 82801BAm ich2-m datasheet 5-111 functional description 22 stalled. 1 = set to a 1 by the ich2 during status updates to indicate that a serious error has occurred at the device/endpoint addressed by this td. this can be caused by babble, the error counter counting down to zero, or reception of the stall handshake from the device during the transaction. any time that a transaction results in the stalled bit being set, the active bit is also cleared (set to 0). if a stall handshake is received from a setup transaction, a time out error will also be reported. 21 data buffer error (dbe). 1 = set to a 1 by the ich2 during status update to indicate that the ich2 is unable to keep up with the reception of incoming data (overrun) or is unable to supply data fast enough during transmission (underrun). when this occurs, the actual length and max length field of the td will not match. in the case of an underrun, the ich2 transmits an incorrect crc (thus invalidating the data at the endpoint) and leaves the td active (unless error count reached zero). if a overrun condition occurs, the ich2 forces a timeout condition on the usb, invalidating the transaction at the source. 20 babble detected (babd). 1 = set to a 1 by the ich2 during status update when ?babble? is detected during the transaction generated by this descriptor. babble is unexpected bus activity for more than a preset amount of time. in addition to setting this bit, the ich2 also sets the? stalled? bit (bit 22) to a 1. since ?babble? is considered a fatal error for that transfer, setting the? stalled? bit to a 1 insures that no more transactions occur as a result of this descriptor. detection of babble causes immediate termination of the current frame. no further tds in the frame are executed. execution resumes with the next frame list index. 19 negative acknowledgment (nak) received (nakr). 1 = set to a 1 by the ich2 during status update when the ich2 receives a ?nak? packet during the transaction generated by this descriptor. if a nak handshake is received from a setup transaction, a time out error is also be reported. 18 crc/time out error (crc_tout). 1 = set to a 1 by the ich2 as follows: during a status update in the case that no response is received from the target device/endpoint within the time specified by the protocol chapter of the usb specification. during a status update when a cycli redundancy check (crc) error is detected during the transaction associated with this transfer descriptor. in the transmit case (out or setup command), this is in response to the ich2 detecting a timeout from the target device/endpoint. in the receive case (in command), this is in response to the ich2?s crc checker circuitry detecting an error on the data received from the device/endpoint or a nak or stall handshake being received in response to a setup transaction. 17 bit stuff error (bse). 1 = this bit is set to a 1 by the ich2 during status update to indicate that the receive data stream contained a sequence of more than 6 ones in a row. 16 bus turn around time-out (btto). 1 = this bit is set to a 1 by the ich2 during status updates to indicate that a bus time-out condition was detected for this usb transaction. this time-out is specially defined as not detecting an idle-to ?k? state start of packet (sop) transition from 16 to 18 bit times after the se0-to ide transition of previous end of packet (eop). 15:11 reserved 10:0 actual length (actlen). the actual length field is written by the ich2 at the conclusion of a usb transaction to indicate the actual number of bytes that were transferred. it can be used by the software to maintain data integrity. the value programmed in this register is encoded as n-1 (see maximum length field description in the td token). table 5-58. td control and status (continued) bit description functional description 5-112 82801BA ich2 and 82801BAm ich2-m datasheet table 5-59. td token bit description 31:21 maximum length (maxlen). the maximum length field specifies the maximum number of data bytes allowed for the transfer. the maximum length value does not include protocol bytes, such as packet id (pid) and crc. the maximum data packet is 1280 bytes. the 1280 packet length is the longest packet theoretically guaranteed to fit into a frame. actual packet maximum lengths are set by hcd according to the type and speed of the transfer. note that the maximum length allowed by the usb specification is 1023 bytes. the valid encodings for this field are: 0x000 = 1 byte 0x001 = 2 bytes .... 0x3fe = 1023 bytes 0x3ff = 1024 bytes .... 0x4ff = 1280 bytes 0x7ff = 0 bytes (null data packet) note that values from 500h to 7feh are illegal and cause a consistency check failure. in the transmit case, the ich2 uses this value as a terminal count for the number of bytes it fetches from host memory. in most cases, this is the number of bytes it will actually transmit. in rare cases, the ich2 may be unable to access memory (e.g., due to excessive latency) in time to avoid underrunning the transmitter. in this instance the ich2 would transmit fewer bytes than specified in the maximum length field. 20 reserved. 19 data toggle (d). this bit is used to synchronize data transfers between a usb endpoint and the host. this bit determines which data pid is sent or expected (0=data0 and 1=data1). the data toggle bit provides a 1-bit sequence number to check whether the previous packet completed. this bit must always be 0 for isochronous tds. 18:15 endpoint (endpt). this 4-bit field extends the addressing internal to a particular device by providing 16 endpoints. this permits more flexible addressing of devices in which more than one sub-channel is required. 14:8 device address. this field identifies the specific device serving as the data source or sink. 7:0 packet identification (pid). this field contains the packet id to be used for this transaction. only the in (69h), out (e1h), and setup (2dh) tokens are allowed. any other value in this field causes a consistency check failure resulting in an immediate halt of the ich2. bits [3:0] are complements of bits [7:4]. table 5-60. td buffer pointer bit description 31:0 buffer pointer (buff_pnt). bits [31:0] corresponds to memory address [31:0], respectively. it points to the beginning of the buffer that will be used during this transaction. this buffer must be at least as long as the value in the maximum length field described int the td token. the data buffer may be byte-aligned. 82801BA ich2 and 82801BAm ich2-m datasheet 5-113 functional description 5.16.1.3 queue head (qh) queue heads are special structures used to support the requirements of control, bulk and interrupt transfers. since these tds are not automatically retired after each use, their maintenance requirements can be reduced by putting them into a queue. queue heads must be aligned on a 16-byte boundary; the elements are shown in table 5-61 . table 5-61. queue head block bytes description attributes 00:03 queue head link pointer ro 04:07 queue element link pointer r/w table 5-62. queue head link pointer bit description 31:4 queue head link pointer (qhlp). this field contains the address of the next data object to be processed in the horizontal list and corresponds to memory address signals [31:4], respectively. 3:2 reserved. these bits must be written as 0s. 1 qh/td select (q). this bit indicates to the hardware whether the item referenced by the link pointer is another td or a qh. 1=qh 0=td 0 terminate (t). this bit indicates to the ich2 that this is the last qh in the schedule. if there are active tds in this queue, they are the last to be executed in this frame. 1 = last qh (pointer is invalid). 0 = pointer is valid (points to a qh or td). table 5-63. queue element link pointer bit description 31:4 queue element link pointer (qelp). this field contains the address of the next td or qh to be processed in this queue and corresponds to memory address signals [31:4], respectively. 3:2 reserved. 1 qh/td select (q). this bit indicates to the hardware whether the item referenced by the link pointer is another td or a qh. for entries in a queue, this bit is typically set to 0. 1 = qh 0 = td 0 terminate (t). this bit indicates to the ich2 that there are no valid tds in this queue. when hcd has new queue entries it overwrites this value with a new td pointer to the queue entry. 1 = terminate (no valid queue entries). 0 = pointer is valid. functional description 5-114 82801BA ich2 and 82801BAm ich2-m datasheet 5.16.2 data transfers to/from main memory the following sections describe the details on how hcd and the ich2 communicate via the schedule data structures. the discussion is organized in a top-down manner, beginning with the basics of walking the frame list, followed by a description of generic processing steps common to all transfer descriptors, and finally a discussion on transfer queuing. 5.16.2.1 executing the schedule software programs the ich2 with the starting address of the frame list and the frame list index, then causes the ich2 to execute the schedule by setting the run/stop bit in the control register to run. the ich2 processes the schedule one entry at a time. the next element in the frame list is not fetched until the current element in the frame list is retired. schedule execution proceeds in the following fashion: ? the ich2 first fetches an entry from the frame list. this entry has three fields. bit 0 indicates whether the address pointer field is valid. bit 1 indicates whether the address points to a transfer descriptor or to a queue head. the third field is the pointer itself. ? if isochronous traffic is to be moved in a given frame, the frame list entry points to a transfer descriptor. if no isochronous data is to be moved in that frame, the entry points to a queue head or the entry is marked invalid and no transfers are initiated in that frame. ? if the frame list entry indicates that it points to a transfer descriptor, the ich2 fetches the entry and begins the operations necessary to initiate a transaction on usb. each td contains a link field that points to the next entry, as well as indicating whether it is a td or a qh. ? if the frame list entry contains a pointer to a qh, the ich2 processes the information from the qh to determine the address of the next data object that it should process. ? the td/qh process continues until the millisecond allotted to the current frame expires. at this point, the ich2 fetches the next entry from the frame list. if the ich2 is not able to process all of the transfer descriptors during a given frame, those descriptors are retired by software without having been executed. 5.16.2.2 processing transfer descriptors the ich2 executes a td using the following generalized algorithm. these basic steps are common across all modes of tds. subsequent sections present processing steps unique to each td mode. 1. ich2 fetches td or qh from the current link pointer. 2. if a qh, go to 1 to fetch from the queue element link pointer. if inactive, go to 12 3. build token, actual bits are in td token. 4. if (host-to-function) then [ pci access ] issue request for data, (referenced through td.bufferpointer) wait for first chunk data arrival end if 5. [ begin usb transaction ] issue token (from token built in 2, above) and begin data transfer. if (host-to-function) then go to 6 else go to 7 end if 6. fetch data from memory (via td bufferpointer) and transfer over usb until td max-length bytes have been read and transferred. [ concurrent system memory and usb accesses ]. go to 8. 82801BA ich2 and 82801BAm ich2-m datasheet 5-115 functional description 7. wait for data to arrive (from usb). write incoming bytes into memory beginning at td bufferpointer. internal hc buffer should signal end of data packet. number of bytes received must be (td max-length; the length of the memory area referenced by td bufferpointer must be (td max-length. [ concurrent system memory and usb accesses ]. 8. issue handshake based on status of data received (ack or time-out). go to 10. 9. wait for handshake, if required [ end of usb transaction ]. 10. update status [ pci access ] (td.status and td.actuallength). if the td was an isochronous td, mark the td inactive. go to 12. if not an isochronous td, and the td completed successfully, mark the td inactive. go to 11. if not successful, and the error count has not been reached, leave the td active. if the error count has been reached, mark the td inactive. go to 12. 11. write the link pointer from the current td into the element pointer field of the qh structure. if the vf bit is set in the td link pointer, go to 2. 12. proceed to next entry. 5.16.2.3 command register, status register, and td status bit interaction notes: 1. only if error counter counted down from 1 to 0 2. suspend mode can be entered only when run/stop bit is 0 table 5-64. command register, status register and td status bit interaction condition ich2 usb status register actions td status register actions crc/time out error set usb error int bit 1 , clear hc halted bit clear active bit 1 and set stall bit 1 illegal pid, pid error, max length (illegal) clear run/stop bit in command register set hc process error and hc halted bits pci master/target abort clear run/stop bit in command register set host system error and hc halted bits suspend mode clear run/stop bit in command register 2 set hc halted bit resume received and suspend mode = 1 set resume received bit run/stop = 0 clear run/stop bit in command register set hc halted bit configuration flag set set configuration flag in command register hc reset/global reset clear run/stop and configuration flag in command register clear usb int, usb error int, resume received, host system error, hc process error, and hc halted bits ioc = 1 in td status set usb int bit stall set usb error int bit clear active bit 1 and set stall bit bit stuff/data buffer error set usb error int bit 1 clear active bit 1 and set stall bit 1 short packet detect set usb int bit clear active bit functional description 5-116 82801BA ich2 and 82801BAm ich2-m datasheet note that, if a nak or stall response is received from a setup transaction, a time out error will be reported. this causes the error counter to decrement and the crc/time-out error status bit to be set within the td control and status dword during write back. if the error counter changes from 1 to 0, the active bit is reset to 0 and stalled bit to 1 as normal. 5.16.2.4 transfer queuing transfer queues are used to implement a guaranteed data delivery stream to a usb endpoint. transfer queues are composed of two parts: a queue header (qh) and a linked list. the linked list of tds and qhs has an indeterminate length (0 to n). the qh contains two link pointers and is organized as two contiguous dwords. the first dword is a horizontal pointer (queue head link pointer), used to link a single transfer queue with either another transfer queue, or a td (target data structure depends on q bit). if the t bit is set, this qh represents the last data structure in the current frame. the t bit informs the ich2 that no further processing is required until the beginning of the next frame. the second dword is a vertical pointer (queue element link pointer) to the first data structure (td or qh) being managed by this qh. if the t bit is set, the queue is empty. this pointer may reference a td or another qh. figure 5-17 illustrates four example queue conditions. the first qh (on far left) is an example of an ?empty? queue; the termination bit (t bit), in the vertical link pointer field, is set to 1. the horizontal link pointer references another qh. the next queue is the expected typical configuration. the horizontal link pointer references another qh, and the vertical link pointer references a valid td. typically, the vertical pointer in a qh points to a td. however, as shown in figure 5-17 (third example from left side of figure) the vertical pointer could point to another qh. when this occurs, a new q context is entered and the q context just exited is null (ich2 does not update the vertical pointer field). the far right qh is an example of a frame ?termination? node. since its horizontal link pointer has its termination bit set, the ich2 assumes there is no more work to complete for the current frame. figure 5-17. example queue conditions t t q t tt eq d q 2 31 1 0 frame list pointer link pointer (horiz) t q t q link pointer (vert) 2 31 1 0 link pointer (horiz) q t q link pointer (vert) 2 31 1 0 link pointer (horiz) q t t link pointer (vert) 2 31 1 0 link pointer (horiz) q t q t link pointer (vert) 2 31 1 0 link pointer (horiz) q q link pointer (vert) 2 31 1 0 link pointer q t td link pointer q td qh qh t indicates "nil" next pointer q td t link pointer q td t link pointer q td indicates "nil" next pointer qh qh indicates "null" queue head 1. link pointer (horiz) = queue head link pointer field in qh dword 0 2. link pointer (vert) = queue element link pointer field in qh dword 1 notes: qh link pointer 82801BA ich2 and 82801BAm ich2-m datasheet 5-117 functional description transfer queues are based on the following characteristics: ? a qh?s vertical link pointer (queue element link pointer) references the ?top? queue member. a qh?s horizontal link pointer (queue head link pointer) references the ?next? work element in the frame. ? each queue member?s link pointer references the next element within the queue. in the simplest model, the ich2 follows vertical link point to a queue element, then executes the element. if the completion status of the td satisfies the advance criteria as shown in table 5-65 , the ich2 advances the queue by writing the just-executed td?s link pointer back into the qh?s queue element link pointer. the next time the queue head is traversed, the next queue element will be the top element. the traversal has two options: breadth first, or depth first. a flag bit in each td (vf - vertical traversal flag) controls whether traversal is breadth or depth first. the default mode of traversal is breadth-first. for breadth-first, the ich2 only executes the top element from each queue. the execution path is shown below: 1. qh (queue element link pointer) 2. td 3. write-back to qh (queue element link pointer) 4. qh (queue head link pointer). breadth-first is also performed for every transaction execution that fails the advance criteria. this means that if a queued td fails, the queue does not advance, and the ich2 traverses the qh?s queue head link pointer. in a depth-first traversal, the top queue element must complete successfully to satisfy the advance criteria for the queue. if the ich2 is currently processing a queue, and the advance criteria are met, and the vf bit is set, the ich2 follows the td?s link pointer to the next schedule work item. note that regardless of traversal model, when the advance criteria are met, the successful td?s link pointer is written back to the qh?s queue element link pointer. when the ich2 encounters a qh, it caches the qh internally, and sets internal state to indicate it is in a q-context. it needs this state to update the correct qh (for auto advancement) and also to make the correct decisions on how to traverse the frame list. restricting the advancement of queues to advancement criteria implements a guaranteed data delivery stream. a queue is never advanced on an error completion status (even in the event the error count was exhausted). table 5-65 lists the general queue advance criteria, which are based on the execution status of the td at the "top" of a currently "active" queue. table 5-65. queue advance criteria function-to-host (in) host-to-function (out) non-null null error/nak non-null null error/nak advance q advance q retry q element advance q advance q retry q element functional description 5-118 82801BA ich2 and 82801BAm ich2-m datasheet table 5-66 is a decision table illustrating the valid combinations of link pointer bits and the valid actions taken when advancement criteria for a queued transfer descriptor are met. the column headings for the link pointer fields are encoded, based on the following list: legends: qh.lp = queue head link pointer (or horizontal link pointer) qe.q = q bit in qe qe.lp = queue element link pointer (or vertical link pointer) qe.t = t bit in qe td.lp = td link pointer td. vf = vf bit in td qh.q = q bit in qh td.q = q bit in td qh.t = t bit in qh td. t = t bit in td q t qhlp qh qt qelp qe vf tdlp td vf q t table 5-66. usb schedule list traversal decision table q context qh.q qh.t qe.q qe.t td.vf td.q td.t description 0----x00 ? not in queue - execute td. ? use td.lp to get next td 0----xx1 ? not in queue - execute td. end of frame 0----x10 ? not in queue - execute td. ? use td.lp to get next (qh+qe). ? set q context to 1. 100000xx ? in queue. use qe.lp to get td. ? execute td. update qe.lp with td.lp. ? use qh.lp to get next td. 1xx00100 ? in queue. use qe.lp to get td. ? execute td. update qe.lp with td.lp. ? use td.lp to get next td. 1xx00110 ? in queue. use qe.lp to get td. ? execute td. update qe.lp with td.lp. ? use td.lp to get next (qh+qe). 100x1xxx ? in queue. empty queue. ? use qh.lp to get next td 1xx10--- ? in queue. use qe.lp to get (qh+qe) 1x1000xx ? in queue. use qe.lp to get td. ? execute td. update qe.lp with td.lp. ? end of frame 1x1x1xxx ? in queue. empty queue. end of frame 82801BA ich2 and 82801BAm ich2-m datasheet 5-119 functional description 5.16.3 data encoding and bit stuffing the usb employs nrzi data encoding (non-return to zero inverted) when transmitting packets. in nrzi encoding, a 1 is represented by no change in level and a 0 is represented by a change in level. a string of zeros causes the nrzi data to toggle each bit time. a string of ones causes long periods with no transitions in the data. to ensure adequate signal transitions, bit stuffing is employed by the transmitting device when sending a packet on the usb. a 0 is inserted after every six consecutive 1s in the data stream before the data is nrzi encoded to force a transition in the nrzi data stream. this gives the receiver logic a data transition at least once every seven bit times to guarantee the data and clock lock. a waveform of the data encoding is shown in figure 5-18 . bit stuffing is enabled beginning with the sync pattern and throughout the entire transmission. the data ?one? that ends the sync pattern is counted as the first one in a sequence. bit stuffing is always enforced, without exception. if required by the bit stuffing rules, a zero bit will be inserted even if it is the last bit before the end-of-packet (eop) signal. 110000xx ? in queue. use qe.lp to get td. ? execute td. update qe.lp with td.lp. ? use qh.lp to get next (qh+qe). 110x1xxx ? in queue. empty queue. ? use qh.lp to get next (qh+qe) table 5-66. usb schedule list traversal decision table (continued) q context qh.q qh.t qe.q qe.t td.vf td.q td.t description figure 5-18. usb data encoding clock data bit stuffed data nrzi data functional description 5-120 82801BA ich2 and 82801BAm ich2-m datasheet 5.16.4 bus protocol 5.16.4.1 bit ordering bits are sent out onto the bus least significant bit (lsb) first, followed by next lsb, through to the most significant bit (msb) last. 5.16.4.2 sync field all packets begin with a synchronization (sync) field, which is a coded sequence that generates a maximum edge transition density. the sync field appears on the bus as idle followed by the binary string ?kjkjkjkk,? in its nrzi encoding. it is used by the input circuitry to align incoming data with the local clock and is defined to be eight bits in length. sync serves only as a synchronization mechanism and is not shown in the following packet diagrams. the last two bits in the sync field are a marker that is used to identify the first bit of the pid. all subsequent bits in the packet must be indexed from this point. 5.16.4.3 packet field formats field formats for the token, data, and handshake packets are described in the following section. the effects of nrzi coding and bit stuffing have been removed for the sake of clarity. all packets have distinct start and end of packet delimiters. packet identifier field a packet identifier (pid) immediately follows the sync field of every usb packet. a pid consists of a four bit packet type field followed by a four-bit check field as shown in table 5-67 . the pid indicates the type of packet and, by inference, the format of the packet and the type of error detection applied to the packet. the four-bit check field of the pid insures reliable decoding of the pid so that the remainder of the packet is interpreted correctly. the pid check field is generated by performing a ones complement of the packet type field. any pid received with a failed check field or which decodes to a non-defined value is assumed to be corrupted and the remainder of the packet is assumed to be corrupted and is ignored by the receiver. pid types, codes, and descriptions are listed in table 5-68 . table 5-67. pid format bit data sent bit data sent 0 pid 0 4 not(pid 0) 1 pid 1 5 not(pid 1) 2 pid 2 6 not(pid 2) 3 pid 3 7 not(pid 3) 82801BA ich2 and 82801BAm ich2-m datasheet 5-121 functional description pids are divided into four coding groups: token, data, handshake, and special, with the first two transmitted pid bits (pid[1:0]) indicating which group. this accounts for the distribution of pid codes. 5.16.4.4 address fields function endpoints are addressed using two fields: the function address field and the endpoint field. address field the function address (addr) field specifies the function, via its address, that is either the source or destination of a data packet, depending on the value of the token pid. as shown in table 5-69 , a total of 128 addresses are specified as addr[6:0]. the addr field is specified for in, setup, and out tokens. table 5-68. pid types pid type pid name pid[3:0] description token out b0001 address + endpoint number in host -> function transaction in b1001 address + endpoint number in function -> host transaction sof b0101 start of frame marker and frame number setup b1101 address + endpoint number in host -> function transaction for setup to a control endpoint data data0 b0011 data packet pid even data1 b1011 data packet pid odd handshake ack b0010 receiver accepts error free data packet nak b1010 rx device cannot accept data or tx device cannot send data stall b1110 endpoint is stalled special pre b1100 host-issued preamble. enables downstream bus traffic to low speed devices. table 5-69. address field bit data sent bit data sent 0 addr 0 4 addr 4 1 addr 1 5 addr 5 2 addr 2 6 addr 6 3 addr 3 functional description 5-122 82801BA ich2 and 82801BAm ich2-m datasheet endpoint field an additional four-bit endpoint (endp) field, shown in table 5-70 , permits more flexible addressing of functions in which more than one sub-channel is required. endpoint numbers are function specific. the endpoint field is defined for in, setup, and out token pids only. 5.16.4.5 frame number field the frame number field is an 11-bit field that is incremented by the host on a per frame basis. the frame number field rolls over upon reaching its maximum value of x7ffh and is sent only for sof tokens at the start of each frame. 5.16.4.6 data field the data field may range from 0 to 1023 bytes and must be an integral numbers of bytes. data bits within each byte are shifted out lsb first. 5.16.4.7 cyclic redundancy check (crc) crc is used to protect the all non-pid fields in token and data packets. in this context, these fields are considered to be protected fields. the pid is not included in the crc check of a packet containing crc. all crcs are generated over their respective fields in the transmitter before bit stuffing is performed. similarly, crcs are decoded in the receiver after stuffed bits have been removed. token and data packet crcs provide 100% coverage for all single and double bit errors. a failed crc is considered to indicate that one or more of the protected fields is corrupted and causes the receiver to ignore those fields, and, in most cases, the entire packet. table 5-70. endpoint field bit data sent 0 endp 0 1 endp 1 2 endp 2 3 endp 3 82801BA ich2 and 82801BAm ich2-m datasheet 5-123 functional description 5.16.5 packet formats 5.16.5.1 token packets table 5-71 shows the field formats for a token packet. a token consists of a pid, specifying either in, out, or setup packet type, and addr and endp fields. for out and setup transactions, the address and endpoint fields uniquely identify the endpoint that will receive the subsequent data packet. for in transactions, these fields uniquely identify which endpoint should transmit a data packet. only the ich2 can issue token packets. in pids define a data transaction from a function to the ich2. out and setup pids define data transactions from the ich2 to a function. token packets have a five-bit crc that covers the address and endpoint fields as shown above. the crc does not cover the pid, which has its own check field. token and sof packets are delimited by an eop after three bytes of packet field data. if a packet decodes as an otherwise valid token or sof but does not terminate with an eop after three bytes, it must be considered invalid and ignored by the receiver. 5.16.5.2 start of frame packets table 5-72 shows a start of frame (sof) packet. sof packets are issued by the host at a nominal rate of once every 1.00 ms. sof packets consist of a pid indicating packet type followed by an 11- bit frame number field. the sof token comprises the token-only transaction that distributes a start of frame marker and accompanying frame number at precisely timed intervals corresponding to the start of each frame. all full speed functions, including hubs, must receive and decode the sof packet. the sof token does not cause any receiving function to generate a return packet; therefore, sof delivery to any given function cannot be guaranteed. the sof packet delivers two pieces of timing information. a function is informed that a start of frame has occurred when it detects the sof pid. frame timing sensitive functions, that do not need to keep track of frame number, need only decode the sof pid; they can ignore the frame number and its crc. if a function needs to track frame number, it must comprehend both the pid and the time stamp. table 5-71. token format packet width pid 8 bits addr 7 bits endp 4 bits crc5 5 bits table 5-72. sof packet packet width pid 8 bits frame number 11 bits crc5 5 bits functional description 5-124 82801BA ich2 and 82801BAm ich2-m datasheet 5.16.5.3 data packets a data packet consists of a pid, a data field, and a crc as shown in table 5-73 . there are two types of data packets identified by differing pids: data0 and data1. two data packet pids are defined to support data toggle synchronization. data must always be sent in integral numbers of bytes. the data crc is computed over only the data field in the packet and does not include the pid, which has its own check field. 5.16.5.4 handshake packets handshake packets consist of only a pid. handshake packets are used to report the status of a data transaction and can return values indicating successful reception of data, flow control, and stall conditions. only transaction types that support flow control can return handshakes. handshakes are always returned in the handshake phase of a transaction and may be returned, instead of data, in the data phase. handshake packets are delimited by an eop after one byte of packet field. if a packet is decoded as an otherwise valid handshake but does not terminate with an eop after one byte, it must be considered invalid and ignored by the receiver. there are three types of handshake packets: ? ack indicates that the data packet was received without bit stuff or crc errors over the data field and that the data pid was received correctly. an ack handshake is applicable only in transactions in which data has been transmitted and where a handshake is expected. ack can be returned by the host for in transactions and by a function for out transactions. ? nak indicates that a function was unable to accept data from the host (out) or that a function has no data to transmit to the host (in). nak can only be returned by functions in the data phase of in transactions or the handshake phase of out transactions. the host can never issue a nak. nak is used for flow control purposes to indicate that a function is temporarily unable to transmit or receive data, but will eventually be able to do so without need of host intervention. nak is also used by interrupt endpoints to indicate that no interrupt is pending. ? stall is returned by a function in response to an in token or after the data phase of an out. stall indicates that a function is unable to transmit or receive data, and that the condition requires host intervention to remove the stall. once a function?s endpoint is stalled, the function must continue returning stall until the condition causing the stall has been cleared through host intervention. the host is not permitted to return a stall under any condition. table 5-73. data packet format packet width pid 8 bits data 0?1023 bytes crc16 16 bits 82801BA ich2 and 82801BAm ich2-m datasheet 5-125 functional description 5.16.5.5 handshake responses in transaction a function may respond to an in transaction with a stall or nak. if the token received was corrupted, the function issues no response. if the function can transmit data, it issues the data packet. the ich2, as the usb host, can return only one type of handshake on an in transaction, an ack. if it receives a corrupted data or cannot accept data due to a condition such as an internal buffer overrun, it discards the data and issues no response. out transaction a function may respond to an out transaction with a stall, ack, or nak. if the transaction contained corrupted data, it will issue no response. setup transaction setup defines a special type of host to function data transaction which permits the host to initialize an endpoint?s synchronization bits to those of the host. upon receiving a setup transaction, a function must accept the data. setup transactions cannot be stalled or naked and the receiving function must accept the setup transfer?s data. if a non-control endpoint receives a setup pid, it must ignore the transaction and return no response. 5.16.6 usb interrupts there are two general groups of usb interrupt sources, those resulting from execution of transactions in the schedule, and those resulting from an ich2 operation error. all transaction- based sources can be masked by software through the ich2?s interrupt enable register. additionally, individual transfer descriptors can be marked to generate an interrupt on completion. when the ich2 drives an interrupt for usb, it drives the pirqd# pin active for interrupts occurring due to ports 0 and 1 until all sources of the interrupt are cleared. 5.16.6.1 transaction based interrupts these interrupts are not signaled until after the status for the last complete transaction in the frame has been written back to host memory. this guarantees that software can safely process through (frame list current index -1) when it is servicing an interrupt. crc error / time-out a crc/time-out error occurs when a packet transmitted from the ich2 to a usb device or a packet transmitted from a usb device to the ich2 generates a crc error. the ich2 is informed of this event by a time-out from the usb device or by the ich2?s crc checker generating an error on reception of the packet. additionally, a usb bus time-out occurs when usb devices do not respond to a transaction phase within 19 bit times of an eop. either of these conditions will cause the c_err field of the td to decrement. when the c_err field decrements to zero, the following occurs: ? the active bit in the td is cleared ? the stalled bit in the td is set ? the crc/time-out bit in the td is set. ? at the end of the frame, the usb error interrupt bit is set in the hc status register. if the crc/time out interrupt is enabled in the interrupt enable register, a hardware interrupt is signaled to the system. functional description 5-126 82801BA ich2 and 82801BAm ich2-m datasheet interrupt on completion transfer descriptors contain a bit that can be set to cause an interrupt on their completion. the completion of the transaction associated with that block causes the usb interrupt bit in the hc status register to be set at the end of the frame in which the transfer completed. when a td is encountered with the ioc bit set to 1, the ioc bit in the hc status register is set to 1 at the end of the frame if the active bit in the td is set to 0 (even if it was set to zero when initially read). if the ioc enable bit of interrupt enable register (bit 2 of i/o offset 04h) is set, a hardware interrupt is signaled to the system. the usb interrupt bit in the hc status register is set either when the td completes successfully or because of errors. if the completion is because of errors, the usb error bit in the hc status register is also set. short packet detect a transfer set is a collection of data which requires more than 1 usb transaction to completely move the data across the usb. an example might be a large print file which requires numerous tds in multiple frames to completely transfer the data. reception of a data packet that is less than the endpoint?s max packet size during control, bulk or interrupt transfers signals the completion of the transfer set, even if there are active tds remaining for this transfer set. setting the spd bit in a td indicates to the hc to set the usb interrupt bit in the hc status register at the end of the frame in which this event occurs. this feature streamlines the processing of input on these transfer types. if the short packet interrupt enable bit in the interrupt enable register is set, a hardware interrupt is signaled to the system at the end of the frame where the event occurred. serial bus babble when a device transmits on the usb for a time greater than its assigned max length, it is said to be babbling. since isochrony can be destroyed by a babbling device, this error results in the active bit in the td being cleared to 0 and the stalled and babble bits being set to one. the c_err field is not decremented for a babble. the usb error interrupt bit in the hc status register is set to 1 at the end of the frame. a hardware interrupt is signaled to the system. if an eof babble was caused by the ich2 (due to incorrect schedule for instance), the ich2 forces a bit stuff error followed by an eop and the start of the next frame. stalled this event indicates that a device/endpoint returned a stall handshake during a transaction or that the transaction ended in an error condition. the tds stalled bit is set and the active bit is cleared. reception of a stall does not decrement the error counter. a hardware interrupt is signaled to the system. data buffer error this event indicates that an overrun of incoming data or a under-run of outgoing data has occurred for this transaction. this would generally be caused by the ich2 not being able to access required data buffers in memory within necessary latency requirements. either of these conditions causes the c_err field of the td to be decremented. when c_err decrements to zero, the active bit in the td is cleared, the stalled bit is set, the usb error interrupt bit in the hc status register is set to 1 at the end of the frame and a hardware interrupt is signaled to the system. 82801BA ich2 and 82801BAm ich2-m datasheet 5-127 functional description bit stuff error a bit stuff error results from the detection of a sequence of more that 6 ones in a row within the incoming data stream. this will cause the c_err field of the td to be decremented. when the c_err field decrements to zero, the active bit in the td is cleared to 0, the stalled bit is set to 1, the usb error interrupt bit in the hc status register is set to 1 at the end of the frame and a hardware interrupt is signaled to the system. 5.16.6.2 non-transaction based interrupts if an ich2 process error or system error occur, the ich2 halts and immediately issues a hardware interrupt to the system. resume received this event indicates that the ich2 received a resume signal from a device on the usb bus during a global suspend. if this interrupt is enabled in the interrupt enable register, a hardware interrupt will be signaled to the system allowing the usb to be brought out of the suspend state and returned to normal operation. ich2 process error the hc monitors certain critical fields during operation to ensure that it does not process corrupted data structures. these include checking for a valid pid and verifying that the maxlength field is less than 1280. if it detects a condition that would indicate that it is processing corrupted data structures, it immediately halts processing, sets the hc process error bit in the hc status register and signals a hardware interrupt to the system. this interrupt cannot be disabled through the interrupt enable register. host system error the ich2 sets this bit to 1 when a pci parity error, pci master abort, or pci target abort occurs. when this error occurs, the ich2 clears the run/stop bit in the command register to prevent further execution of the scheduled tds. this interrupt cannot be disabled through the interrupt enable register. 5.16.7 usb power management the host controller can be put into a suspended state and its power can be removed. this requires that certain bits of information are retained in the resume power plane of the ich2 so that a device on a port may wake the system. such a device may be a fax-modem, that wakes up the machine to receive a fax or takes a voice message. the settings of the following bits in i/o space is maintained when the ich2 enters the s3, s4 or s5 states. when the ich2 detects a resume event on any of its ports, it sets the corresponding usb_sts bit in acpi space. if usb is enabled as a wake/break event, the system wakes up and an sci is generated. table 5-74. bits maintained in low power states register offset bit description command 00h 3 enter global suspend mode (egsm) status 02h 2 resume detect port status and control 10h & 12h 2 port enabled/disabled 6 resume detect 8 low speed device attached 12 suspend functional description 5-128 82801BA ich2 and 82801BAm ich2-m datasheet 5.16.8 usb legacy keyboard operation when a usb keyboard is plugged into the system and a standard keyboard is not, the system may not boot and dos legacy software will not run; this is because the keyboard is not identified. the ich2 implements a series of trapping operations which snoop accesses that go to the keyboard controller and put the expected data from the usb keyboard into the keyboard controller. note: the scheme described below assumes that the keyboard controller (8042 or equivalent) is on the lpc bus. this legacy operation is performed through smm space. figure 5-19 shows the enable and status path. the latched smi source (60r, 60w, 64r, 64w) is available in the status register. because the enable is after the latch, it is possible to check for other events that didn't necessarily cause an smi. it is the software's responsibility to logically and the value with the appropriate enable bits. note also that the smi is generated before the pci cycle completes (e.g., before trdy# goes active) to ensure that the processor does not complete the cycle before the smi is observed. this method is used on mpiix and has been validated. the logic will also need to block the accesses to the 8042. if there is an external 8042, this is accomplished by not activating the 8042 cs. this is done by logically anding the 4 enables (60r, 60w, 64r, 64w) with the 4 types of accesses to determine if the 8042cs should go active. an additional term is required for the ?pass-through? case. the state table for the diagram is shown in table 5-75 . figure 5-19. usb legacy keyboard flow diagram decoder pci config read, write comb. and 60 read en_smi_on_60r s clear smi_60_r r d or smi same for 60w, 64r, 64w to individual "caused by" "bits" kbc accesses and usb_irq en_smi_on_irq s clear usb_irq r d to "caused by" bit to pirqd# and en_pirqd# 82801BA ich2 and 82801BAm ich2-m datasheet 5-129 functional description table 5-75. usb legacy keyboard state transitions current state action data value next state comment idle 64h / write d1h gatestate1 standard d1 command. cycle passed through to 8042. smi# doesn't go active. pstate goes to 1. idle 64h / write not d1h idle bit 3 in configuration register determines if cycle passed through to 8042 and if smi# generated. idle 64h / read n/a idle bit 2 in configuration register determines if cycle passed through to 8042 and if smi# generated. idle 60h / write don't care idle bit 1 in configuration register determines if cycle passed through to 8042 and if smi# generated. idle 60h / read n/a idle bit 0 in configuration register determines if cycle passed through to 8042 and if smi# generated. gatestate1 60h / write xxh gatestate2 cycle passed through to 8042, even if trap enabled in bit 1 in configuration register. no smi# generated. pstate remains 1. if data value is not dfh or ddh then the 8042 may chose to ignore it. gatestate1 64h / write d1h gatestate1 cycle passed through to 8042, even if trap enabled via bit 3 in configuration register. no smi# generated. pstate remains 1. stay in gatestate1 because this is part of the double- trigger sequence. gatestate1 64h / write not d1h ilde bit 3 in configuration space determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in configuration register is set, then smi# should be generated. gatestate1 60h / read n/a idle this is an invalid sequence. bit 0 in configuration register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in configuration register is set, then smi# should be generated. gatestate1 64h / read n/a gatestate1 just stay in same state. generate an smi# if enabled in bit 2 of configuration register. pstate remains 1. gatestate2 64 / write ffh idle standard end of sequence. cycle passed through to 8042. pstate goes to 0. bit 7 in configuration space determines if smi# should be generated. gatestate2 64h / write not ffh idle improper end of sequence. bit 3 in configuration register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in configuration register is set, then smi# should be generated. gatestate2 64h / read n/a gatestate2 just stay in same state. generate an smi# if enabled in bit 2 of configuration register. pstate remains 1. gatestate2 60h / write xxh idle improper end of sequence. bit 1 in configuration register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in configuration register is set, then smi# should be generated. gatestate2 60h / read n/a idle improper end of sequence. bit 0 in configuration register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in configuration register is set, then smi# should be generated. functional description 5-130 82801BA ich2 and 82801BAm ich2-m datasheet 5.17 smbus controller functional description (d31:f3) the ich2 provides an smbus host controller as well as an smbus slave interface. the host controller provides a mechanism for the processor to initiate communications with smbus peripherals (slaves). the ich2 is also capable of operating in a mode in which it can communicate with i 2 c compatible devices. the slave interface allows an external master to read from or write to the ich2. write cycles can be used to cause certain events or pass messages and the read cycles can be used to determine the state of various status bits. the ich2?s internal host controller cannot access the ich2?s internal slave interface. the ich2 smbus logic exists in device 31:function 3 configuration space and consists of a transmit data path and host controller. the transmit data path provides the data flow logic needed to implement the seven different smbus command protocols and is controlled by the host controller. the ich2 smbus controller logic is clocked by rtc clock. the programming model of the host controller is combined into two portions: a pci configuration portion and a system i/o mapped portion. all static configuration (e.g., the i/o base address) is done via the pci configuration space. real-time programming of the host interface is done in system i/o space. 5.17.1 host controller the smbus host controller is used to send commands to other smbus slave devices. software sets up the host controller with an address, command, and, for writes, data, and then tells the controller to start. when the controller has finished transmitting data on writes, or receiving data on reads, it will generate an smi# or interrupt, if enabled. the host controller supports 7 command protocols of the smbus interface (see system management bus specification, rev 1.0): quick command, send byte, receive byte, write byte/ word, read byte/word, process call, and block read/write. the smbus host controller requires that the various data and command fields be setup for the type of command to be sent. when software sets the start bit, the smbus host controller performs the requested transaction and interrupts the processor (or generate an smi#) when the transaction is completed. once a start command has been issued, the values of the ?active registers? (host control, host command, transmit slave address, data 0, data 1) should not be changed or read until the interrupt status bit (intr) has been set (indicating the completion of the command). any register values needed for computation purposes should be saved prior to issuing of a new command, as the smbus host controller will update all registers while completing the new command. using the smb host controller to send commands to the ich2's smb slave port is not supported. 82801BA ich2 and 82801BAm ich2-m datasheet 5-131 functional description 5.17.1.1 command protocols in all of the following commands, the host status register (offset 00h) is used to determine the progress of the command. while the command is in operation, the host_busy bit is set. if the command completes successfully, the intr bit is set in the host status register. if the device does not respond with an acknowledge and the transaction times out, the dev_err bit is set. if software sets the kill bit in the host control register while the command is running, the transaction will stop and the failed bit will be set. quick command when programmed for a quick command, the transmit slave address register is sent. the format of the protocol is shown in table 5-76 . send byte / receive byte for the send byte command, the transmit slave address and device command registers are sent for the receive byte command, the transmit slave address register is sent. the data received is stored in the data0 register. the receive byte is similar to a send byte; the only difference is the direction of data transfer. the format of the protocol is shown in table 5-77 . write byte/word the first byte of a write byte/word access is the command code. the next 1 or 2 bytes are the data to be written. when programmed for a write byte/word command, the transmit slave address, device command and data0 registers are sent. in addition, the data1 register is sent on a write word command. the format of the protocol is shown in table 5-78 . table 5-76. quick protocol bit description 1 start condition 2:8 slave address - 7 bits 9 read / write direction 10 acknowledge from slave 11 stop table 5-77. send / receive byte protocol send byte protocol receive byte protocol bit description bit description 1start 1 start 2:8 slave address - 7 bits 2:8 slave address - 7 bits 9write 9 read 10 acknowledge from slave 10 acknowledge from slave 11:18 command code - 8 bits 11:18 data byte from slave 19 acknowledge from slave 19 not acknowledge 20 stop 20 stop functional description 5-132 82801BA ich2 and 82801BAm ich2-m datasheet read byte/word reading data is slightly more complicated than writing data. first the ich2 must write a command to the slave device. then it must follow that command with a repeated start condition to denote a read from that device's address. the slave then returns 1 or 2 bytes of data. when programmed for the read byte/word command, the transmit slave address and device command registers are sent. data is received into the data0 on the read byte, and the dat0 and data1 registers on the read word. the format of the protocol is shown in table 5-79 . table 5-78. write byte/word protocol write byte protocol write word protocol bit description bit description 1 start 1 start 2:8 slave address - 7 bits 2:8 slave address - 7 bits 9 write 9 write 10 acknowledge from slave 10 acknowledge from slave 11:18 command code - 8 bits 11:18 command code - 8 bits 19 acknowledge from slave 19 acknowledge from slave 20:27 data byte - 8 bits 20:27 data byte low - 8 bits 28 acknowledge from slave 28 acknowledge from slave 29 stop 29:36 data byte high - 8 bits 37 acknowledge from slave 38 stop table 5-79. read byte/word protocol read byte protocol read word protocol bit description bit description 1start 1start 2:8 slave address - 7 bits 2:8 slave address - 7 bits 9write 9write 10 acknowledge from slave 10 acknowledge from slave 11:18 command code - 8 bits 11:18 command code - 8 bits 19 acknowledge from slave 19 acknowledge from slave 20 repeated start 20 repeated start 21:27 slave address - 7 bits 21:27 slave address - 7 bits 28 read 28 read 29 acknowledge from slave 29 acknowledge from slave 30:37 data from slave - 8 bits 30:37 data byte low from slave - 8 bits 38 not acknowledge 38 acknowledge 39 stop 39:46 data byte high from slave - 8 bits 47 not acknowledge 48 stop 82801BA ich2 and 82801BAm ich2-m datasheet 5-133 functional description process call the process call is so named because a command sends data and waits for the slave to return a value dependent on that data. the protocol is simply a write word followed by a read word, but without a second command or stop condition. when programmed for the process call command, the ich2 transmits the transmit slave address, host command, data0 and data1 registers. data received from the device is stored in the data0 and data1 registers. the format of the protocol is shown in table 5-80 . note: for process call command, the value written into bit 0 of the transmit slave address register (smb i/o register, offset 04h) needs to be 0. table 5-80. process call protocol bit description 1start 2:8 slave address - 7 bits 9write 10 acknowledge from slave 11:18 command code - 8 bits 19 acknowledge from slave 20:27 data byte low - 8 bits 28 acknowledge from slave 29:36 data byte high - 8 bits 37 acknowledge from slave 38 repeated start 39:45 slave address - 7 bits 46 read 47 acknowledge from slave 48:55 data byte low from slave - 8 bits 56 acknowledge 57:64 data byte high from slave - 8 bits 65 not acknowledge 66 stop functional description 5-134 82801BA ich2 and 82801BAm ich2-m datasheet block read/write the block write begins with a slave address and a write condition. after the command code, the ich2 issues a byte count which describes how many more bytes will follow in the message. if a slave had 20 bytes to send, the first byte would be the number 20 (14h), followed by the 20 bytes of data. the byte count may not be 0. note that, unlike the piix4, which implements 32-byte buffer for block read/write command, the ich2 implements the block data byte register (d31:f3, i/o offset 07h) for block read/write command. when programmed for a block write command, the transmit slave address, host command, and data0 (count) registers are sent. data is then sent from the block data byte register. after the byte has been sent, the ich2 sets the byte_done_sts bit in the host status register. if there are more bytes to send, software writes the next byte to the block data byte register and also clears the byte_done_sts bit. the ich2 then sends the next byte. when doing a block write, first poll the byte_done_sts register until it is set, then write the next byte, then clear the byte_done_sts register. on block read commands, after the byte count is stored in the data 0 register, the first data byte goes in the block data byte register; the ich2 will then set the byte_done_sts bit and generate an smi# or interrupt. the smi# or interrupt handler reads the byte and then clears the byte_done_sts bit to allow the next byte to be read into the block data byte register. note that after receiving data byte n-1 of the block, the software needs to set the last_byte bit in the host control register; this allows the ich2 to send a not ack (instead of an ack) after receiving the last data byte (byte n) of the block. after each byte of a block message the ich2 sets the byte_done_sts bit and generates an interrupt or smi#. software clears the byte_done_sts bit before the next transfer occurs. when the interrupt handler clears the byte_done_sts bit after the last byte has been transferred, the ich2 sets the intr bit and generates another interrupt to signal the end of the block transfer. thus, for a block message of n bytes, the ich2 generates n+1 interrupts. the interrupt handler needs to be implemented to handle all of these interrupts the format of the block read/write protocol is shown in table 5-81 . note: for block write, if the i 2 c_en bit is set, the format of the command changes slightly. the ich2 still sends the number of bytes indicated in the data0 register. however, it does not send the contents of the data 0 register as part of the message. 82801BA ich2 and 82801BAm ich2-m datasheet 5-135 functional description l i 2 c read this command allows the ich2 to perform block reads to certain i 2 c devices (e.g., serial e 2 proms). the smbus block read sends both the 7-bit address, as well as the command field. this command field could be used as the extended 10-bit address for accessing i 2 c devices that use 10-bit addressing. however, this does not allow access to devices using the i 2 c ?combined format? that has data bytes after the address. typically, these data bytes correspond to an offset (address) within the serial memory chips. note: this new command is supported independent of the setting of the i 2 c_en bit. for i 2 c read command, the value written into bit 0 of the transmit slave address register (smb i/o register, offset 04h) needs to be 0. the format that is used for the new command is shown in table 5-82 : table 5-81. block read/write protocol block write protocol block read protocol bit description bit description 1 start 1 start 2:8 slave address - 7 bits 2:8 slave address - 7 bits 9 write 9 write 10 acknowledge from slave 10 acknowledge from slave 11:18 command code - 8 bits 11:18 command code - 8 bits 19 acknowledge from slave 19 acknowledge from slave 20:27 byte count - 8 bits (skip this step if i 2 c_en bit set) 20 repeated start 28 acknowledge from slave (skip this step if i2c_en bit set) 21:27 slave address - 7 bits 29:36 data byte 1 - 8 bits 28 read 37 acknowledge from slave 29 acknowledge from slave 38:45 data byte 2?8 bits 30:37 byte count from slave - 8 bits 46 acknowledge from slave 38 acknowledge ... data bytes / slave acknowledges... 39:46 data byte 1 from slave - 8 bits ... data byte n - 8 bits 47 acknowledge ... acknowledge from slave 48:55 data byte 2 from slave - 8 bits ... stop 56 acknowledge ... data bytes from slave/acknowledge ... data byte n from slave - 8 bits ... not acknowledge ... stop functional description 5-136 82801BA ich2 and 82801BAm ich2-m datasheet the ich2 continues reading data from the peripheral until the nak is received. 5.17.1.2 i 2 c behavior when the i 2 c_en bit is set, the ich2 smbus logic is instead set to communicate with i 2 c devices. this forces the following changes: 1. the process call command will skip the command code (and its associated acknowledge) 2. the block write command will skip sending the byte count (data0) in addition, the ich2 supports the new i 2 c read command. this is independent of the i 2 c_en bit. 5.17.1.3 heartbeat for use with the external lan controller this method allows the ich2 to send messages to an external lan controller when the processor is otherwise unable to do so. it uses the smlink i/f between the ich2 and the external lan controller. the actual heartbeat message is a block write. only 8 bytes are sent. table 5-82. i 2 c block read bit description 1start 2:8 slave address - 7 bits 9write 10 acknowledge from slave 11:18 command code - 8 bits 19 acknowledge from slave 20:27 send data0 register 28 acknowledge from slave 29:36 send data1 register 37 acknowledge from slave 38 repeated start 39:45 slave address - 7 bits 46 read 47 acknowledge from slave 48:55 data byte from slave 56 acknowledge 57:64 data byte 2 from slave - 8 bits 65 acknowledge - data bytes from slave / acknowledge - data byte n from slave - 8 bits - not acknowledge -stop 82801BA ich2 and 82801BAm ich2-m datasheet 5-137 functional description 5.17.2 bus arbitration several masters may attempt to get on the bus at the same time by driving the smbdata line low to signal a start condition. the ich2 continuously monitors the smbdata line. when the ich2 is attempting to drive the bus to a 1 by letting go of the smbdata line and it samples smbdata low, then some other master is driving the bus and the ich2 stops transferring data. if the ich2 sees that it has lost arbitration, the condition is called a collision. the ich2 sets the bus_err bit in the host status register, and, if enabled, generates an interrupt or smi#. the processor is responsible for restarting the transaction. when the ich2 is a smbus master, it drives the clock. when the ich2 is sending address or command as an smbus master or data bytes as a master on writes, it drives data relative to the clock it is also driving. it does not start toggling the clock until the start or stop condition meets proper setup and hold time. the ich2 also guarantees minimum time between smbus transactions as a master. the ich2 supports the same arbitration protocol for both the smbus and the system management (smlink) interfaces. clock stretching some devices may not be able to handle their clock toggling at the rate that the ich2, as an smbus master, would like. they have the capability of stretching the low time of the clock. when the ich2 attempts to release the clock (allowing the clock to go high), the clock will remain low for an extended period of time. the ich2 monitors the smbus clock line after it releases the bus to determine whether to enable the counter for the high time of the clock. while the bus is still low, the high time counter must not be enabled. similarly, the low period of the clock can be stretched by an smbus master if it is not ready to send or receive data. the ich2 smbus host controller will never stretch the low period of the clock (smbclk). it always has the data to transfer on writes and it always has a spot for the data on reads. the smlink interface, however, always stretches the low period of the clock, effectively forcing transfers down to 16 khz. bus time out (ich2 as smbus master) if there is an error in the transaction, such that an smbus device does not signal an acknowledge or holds the clock lower than the allowed time-out time, the transaction times out. the ich2 discards the cycle and sets the dev_err bit. the time-out minimum is 25 ms. the time-out counter inside the ich2 starts after the last bit of data is transferred by the ich2 and it is waiting for a response. the 25 ms is a count of 800 rtc clocks. 5.17.3 interrupts / smi# the ich2 smbus controller uses pirqb# as its interrupt pin. however, the system can alternatively be set up to generate smi# instead of an interrupt, by setting the smbus_smi_en bit. functional description 5-138 82801BA ich2 and 82801BAm ich2-m datasheet 5.17.4 smbalert# smbalert# is multiplexed with gpio[11]. when enabled and the signal is asserted, the ich2 can generate an interrupt, an smi#, or a wake event from s1-s4. to resume using smbalert#, the smb_smi_en bit must be enabled to generate an smi (see section 12.1.14, ?hostc?host configuration register (smbus?d31:f3)? on page 12-5 ). note: as long as smbalert# is enabled and asserted, the ich2 will continue to assert pirq[b]# or smi# (depending on the state of the smb_smi_en bit). to avoid continuous smis or interrupts, the interrupt or smi handler should: 1. disable smbalert# by setting gpio_use_sel[11] (gpiobase + 00h, bit 11) 2. use the smbus host controller to service the peripheral that is asserting smbalert# (causing the device to deassert the signal) 3. re-enable smbalert# by clearing gpio_use_sel[11]. 5.17.5 smbus slave interface the ich2?s smbus slave interface is accessed via the smlink[1:0] signals. the slave interface allows the ich2 to decode cycles and allows an external microcontroller to perform specific actions. key features and capabilities include: ? supports decode of two messages type: write and read ? receive slave address register: this is the address that the ich2 decodes. a default value is provided so that the slave interface can be used without the processor having to program this register. ? receive slave data register in the smbus i/o space that includes the data written by the external microcontroller ? registers that the external microcontroller can read to get the state of the ich2. see table 5-87 ? status bit to indicate that the smbus logic caused an smi# due to the reception of a message that matched the slave address. see section 9.8.3.14 . 82801BA ich2 and 82801BAm ich2-m datasheet 5-139 functional description format of slave write cycle the external master performs byte write commands to the ich2 smbus slave i/f. the ?command? field (bits 11-18) indicate which register is being accessed. the data field (bits 20-27) indicate the value that should be written to that register. the write cycle format is shown in table 5-83 . table 5-84 lists the values associated with the registers. note: the external microcontroller is responsible to make sure that it does not update the contents of the data byte registers until they have been read by the system processor. the ich2 overwrites the old value with any new value received. a race condition is possible where the new value is being written to the register just at the time it is being read. ich2 will not attempt to cover this race condition (i.e., unpredictable results in this case). table 5-83. slave write cycle format bits description driven by comment 1 start condition external microcontroller 2:8 slave address - 7 bits external microcontroller must match value in receive slave address register 9 write external microcontroller always 0 10 ack ich2 11:18 command external microcontroller this field indicates which register will be accessed. see table 5-84 below for the register definitions 19 ack ich2 20:27 register data external microcontroller see table 5-84 below for the register definitions 28 ack ich2 29 stop external microcontroller table 5-84. slave write registers register function 0 command register. see table 65 below for legal values written to this register. 1?3 reserved 4 data message byte 0 5 data message byte 1 6?7 reserved 8 frequency straps will be written on bits 3:0. bits 7:4 should be 0, but will be ignored. 9?ffh reserved functional description 5-140 82801BA ich2 and 82801BAm ich2-m datasheet format of read command the external master performs byte read commands to the ich2 smbus slave interface. the ?command? field (bits 11:18) indicate which register is being accessed. the data field (bits 30:37) contain the value that should be read from that register. table 5-86 shows the read cycle format. table 5-87 shows the register mapping for the data byte. table 5-85. command types command type description 0 reserved 1 wake/smi#: wake system if it is not already awake. if the system is already awake, an smi# is generated. note that the smb_wak_sts bit will be set by this command, even if the system is already awake. the smi handler should then clear this bit. 2 unconditional powerdown: this command sets the pwrbtnor_sts bit and has the same effect as the powerbutton override occurring. this functionality depends upon the bios having cleared the pwrbtn_sts bit. 3 hard reset without cycling: this causes a hard reset of the system (does not include cycling of the power supply). this is equivalent to a write to the cf9h register with bits 2:1 set to 1, but bit 3 set to 0. 4 hard reset system: this causes a hard reset of the system (including cycling of the power supply). this is equivalent to a write to the cf9h register with bits 3:1 set to 1. 5 disable the tco messages. this command disables the ich2 from sending heartbeat and event messages (as described in section 5.13.2 ). once this command has been executed, heartbeat and event message reporting can only be re-enabled by assertion and deassertion of the rsmrst# signal. 6 wd reload: reload watchdog timer. 7?ffh reserved table 5-86. read cycle format bit description driven by comment 1 start external microcontroller 2:8 slave address - 7 bits external microcontroller must match value in receive slave address register 9 write external microcontroller always 0 10 ack ich2 11:18 command code ? 8 bits external microcontroller indicates which register is being accessed. see table 5-87 . 19 ack ich2 20 repeated start external microcontroller 21:27 slave address - 7 bits external microcontroller must match value in receive slave address register 28 read external microcontroller always 1 29 ack ich2 30:37 data byte ich2 value depends on register being accessed. see table 5-87 . 38 not ack external microcontroller 39 stop ich2 82801BA ich2 and 82801BAm ich2-m datasheet 5-141 functional description behavioral notes according to smbus protocol, read and write messages always begin with a start bit - address - write bit sequence. when the ich2 detects that the address matches the value in the receive slave address register, it assumes that the protocol is always followed and ignores the write bit (bit 9) and signal an acknowledge during bit 10 (see table 5-83 and table 5-86 ). in other words, if a start - address - read occurs (which is illegal for smbus read or write protocol), and the address matches the ich2?s slave address, the ich2 will still grab the cycle. also according to smbus protocol, a read cycle contains a repeated start - address - read sequence beginning at bit 20 (see table 5-86 ). once again, if the address matches the ich2?s receive slave address, it will assume that the protocol is followed, ignore bit 28, and proceed with the slave read cycle. note: an external microcontroller must not attempt to access the ich2?s smbus slave logic until at least 1 second after both rtcrst# and rsmrst# are deasserted (high). table 5-87. data values for slave read registers register bits description 0 7:0 reserved. 12:0 system power state 000 = s0 001 = s1 010 = reserved 011 = s3 100 = s4 101 = s5 110 = reserved 111 = reserved 17:3reserved 2 3:0 frequency strap register 27:4reserved 3 5:0 watchdog timer current value 37:6reserved 40 1 = the intruder detect (intrd_det) bit is set. this indicates that the system cover has probably been opened. 41 1 = bti temperature event occurred. this bit is set if the ich2?s thrm# input signal is active. need to take after polarity control. 4 2 doa processor status. this bit is 1 to indicate that the processor is dead. 4 3 1 = watchdog timer expired. this bit is set if the ich2?s tco timers have timed out. 4 6:4 reserved. 4 7 will reflect the state of the ich2?s gpio[11]. 5 0 unprogrammed fwh bit. this bit will be 1 to indicate that the first bios fetch returned ffh, which indicates that the fwh is probably blank. 57:1reserved 6 7:0 contents of the message 1 register. see section 9.9.10 . 7 7:0 contents of the message 2 register. see section 9.9.10 . 8 7:0 contents of the wdstatus register. see section 9.9.11 . 9?ffh 7:0 reserved functional description 5-142 82801BA ich2 and 82801BAm ich2-m datasheet 5.18 ac?97 controller functional description (audio d31:f5, modem d31:f6) note: all references to ac?97 in this document refer to the ac?97 2.1 specification. for further information on the operation of the ac-link protocol, see the ac?97 specification. the ich2 ac ?97 controller features include: ? independent pci functions for audio and modem. ? independent bus master logic for mic input, pcm audio input (2-channel stereo), pcm audio output (2, 4 or 6-channel stereo), modem input and modem output. ? 16 bit sample resolution ? multiple sample rates up to 48 khz ? 16 gpios ? single modem line ? dual codec configuration with two sdin pins table 5-88 shows a detailed list of features supported by the ich2 ac?97 digital controller. . table 5-88. featured supported by ich2 feature description system interface ? isochronous low latency bus master memory interface ? scatter/gather support for word-aligned buffers in memory (all mono or stereo 16-bit data types are supported, no 8-bit data types are supported) ? data buffer size in system memory from 3 to 65535 samples per input ? data buffer size in system memory from 0 to 65535 samples per output ? independent pci audio and modem functions with configuration and io spaces ? ac?97 codec registers are shadowed in system memory via driver (not pci io space) ? ac?97 codec register accesses are serialized via semaphore bit in pci io space (new accesses are not allowed while a prior access is still in progress) power management ? power management via acpi control methods support for audio states: d0, d2, d3hot, d3cold support for modem states: d0, d3hot, d3cold ? sci event generation for pci modem function with wake-up from d3cold ? independent codec d3 w/ link down event, synchronized via two bit semaphore (in pci io space) pci audio function ? read/write access to audio codec registers 00h-3ah and vendor registers 5ah?7eh ? 16-bit stereo pcm output, up to 48 khz (l,r, center, sub-woofer, l-rear and r-rear channels on slots 3,4,6,7,8.9) ? 16-bit stereo pcm input, up to 48 khz (l,r channels on slots 3,4) ? 16-bit mono mic in w/ or w/o mono mix, up to 48 khz (l,r channel, slots 3,4) (mono mix supports mono hardware aec reference for speakerphone) ? 16-bit mono pcm input, up to 48 khz from dedicated mic adc (slot 6) (supports speech recognition or stereo hardware aec ref for speakerphone) ? during cold reset ac_rst# is held low until after post and software deassertion of ac_rst# (supports passive pc_beep to speaker connection during post) 82801BA ich2 and 82801BAm ich2-m datasheet 5-143 functional description note: throughout this document, references to d31:f5 indicate that the audio function exists in pci device 31, function 5. references to d31:f6 indicate that the modem function exists in pci device 31, function 6. 5.18.1 ac-link overview the ich2 is an ac?97 2.1 compliant controller that communicates with companion codecs via a digital serial link called the ac-link. all digital audio/modem streams and command/status information is communicated over the ac-link. the ac-link is a bi-directional, serial pcm digital stream. it handles multiple input and output data streams, as well as control register accesses, employing a time division multiplexed (tdm) scheme. the ac-link architecture provides for data transfer through individual frames transmitted in a serial fashion. each frame is divided into 12 outgoing and 12 incoming data streams, or slots. the architecture of the ich2 ac-link allows a maximum of two codecs to be connected. figure 5-21 shows a two codec topology of the ac-link for the ich2. pci modem function ? read/write access to modem codec registers 3ch-58h and vendor registers 5ah?7eh ? 16-bit mono modem line1 output and input, up to 48 khz (slot 5) ? low latency gpio[13:11,8:6,4:3,1:0] (gpio[13:11,8:7,4:3,1:0] for the ich2-m) via hardwired update between slot 12 and pci io register ? programmable pci interrupt on modem gpio input changes via slot 12 gpio_int ? sci event generation on primary or secondary sdin wake-up signal ac-link ? ac?97 2.1 compliant ac-link interface ? variable sample rate output support via ac?97 slotreq protocol (slots 3,4,5,6,7,8,9) ? variable sample rate input support via monitoring of slot valid tag bits (slots 3,4,5,6) ? 3.3 v digital operation meets ac?97 2.1 dc switching levels ? ac-link io driver capability meets ac?97 2.1 dual codec specifications ? codec register status reads must be returned with data in the next ac-link frame, per ac?97 2.1 specification. multiple codec ? dual codec addressing: all ac?97 codec register accesses are addressable to codec id 00 (primary) or codec id 01 (secondary) ? dual codec receive capability via primary and secondary sdin pins (primary, secondary sdin frames are internally validated, synchronized, and or?d) figure 5-20. ich2 based ac?97 2.1 table 5-88. featured supported by ich2 (continued) feature description audio in (record) audio out (playback) modem pc mic. functional description 5-144 82801BA ich2 and 82801BAm ich2-m datasheet the ac-link consists of a five signal interface between the controller and codec. table 5-89 indicates the ac-link signal pins on the ich2 and their associated power wells. note: power well voltage levels are 3.3v ich2 core well outputs may be used as strapping options for the ich2, sampled during system reset. these signals may have weak pull-ups/put-downs; however, this will not interfere with link operation. ich2 inputs integrate weak put-downs to prevent floating traces when a secondary codec is not attached. when the shut off bit in the control register is set, all buffers will be turned off and the pins will be held in a steady state, based on these pull-ups/put-downs. bit_clk is fixed at 12.288 mhz and is sourced by the primary codec. it provides the necessary clocking to support the twelve 20 bit time slots. ac-link serial data is transitioned on each rising edge of bit_clk. the receiver of ac-link data samples each serial bit on the falling edge of bit_clk. synchronization of all ac-link data transactions is signaled by the ac?97 controller via the ac_sync signal, as shown in figure 5-22 . the primary codec drives the serial bit clock onto the ac-link, which the ac?97 controller then qualifies with the ac_sync signal to construct data frames. ac_sync, fixed at 48 khz, is derived by dividing down bit_clk. ac_sync remains figure 5-21. ac?97 2.1 controller-codec connection digital ac '97 2.1 controller ac '97 2.1 controller section of the ich2 primary codec sync bit_clk sdout ac '97 / ac' 97 2.1 / amc '97 2.1 reset# sdin 0 secondary codec sdin 1 ac '97 / mc '97 2.1 / amc '97 2.1 table 5-89. ac?97 signals signal name type power well* description ac_reset# output resume master hardware reset ac_sync output core 48 khz fixed rate sample sync ac_bit_clk input core 12.288 mhz serial data clock ac_sdout output core serial output data ac_sdin 0 input resume serial input data ac_sdin 1 input resume serial input data 82801BA ich2 and 82801BAm ich2-m datasheet 5-145 functional description high for a total duration of 16 bit_clks at the beginning of each frame. the portion of the frame where ac_sync is high is defined as the tag phase. the remainder of the frame where ac_sync is low is defined as the data phase. each data bit is sampled on the falling edge of bit_clk. the ich2 has two sdin pins allowing a single or dual codec configuration. when two codecs are connected, the primary and secondary codecs can be connected to either sdin line, however it is recommended that the primary codec be attached to sdin [0]. the ich2 does not distinguish between primary and secondary codecs on its sdin[1:0] pins; however, the registers do distinguish between sdin[0] and sdin[1] for wake events, etc. the primary codec can be an ac (audio codec), mc (modem codec), or amc (audio/modem codec) device. the secondary codec can be an ac, mc, or amc device. the mc can be either on the primary or the secondary codec, while the ac can be either on the primary or the secondary codec, or both the primary or the secondary codec. the ich2 does not support optional test modes as outlined in the ac?97 specification. ac-link output frame (sdout) a new audio output frame begins with a low to high transition of ac_sync. ac_sync is synchronous to the rising edge of bit_clk. on the immediately following falling edge of bit_clk, the codec samples the assertion of ac_sync. this falling edge marks the time when both sides of ac-link are aware of the start of a new frame. on the next rising edge of bit_clk, the ich2 transitions sdout into the first bit position of slot 0, or the valid frame bit. each new bit position is presented to the ac-link on a rising edge of bit_clk, and subsequently sampled by the codec on the following falling edge of bit_clk. this sequence ensures that data transitions and subsequent sample points for both incoming and outgoing data streams are time aligned. the output frame data phase corresponds to the multiplexed bundles of all digital output data targeting codec dac inputs and control registers. each output frame supports up to twelve outgoing data time slots. the ich2 generates 16 bit samples and, in compliance with the ac?97 specification, pads the 4 least significant bits of valid slots with zeros. the output data stream is sent with the most significant bit first and all invalid slots are stuffed with 0s. when mono audio sample streams are output from the ich2, software must ensure both left and right sample stream time slots are filled with the same data. output slot 0: tag phase slot 0 is considered the tag phase. the tag phase is a special 16 bit time slot wherein each bit conveys a valid tag for its corresponding time slot within the current frame. a one in a given bit position of slot 0 indicates that the corresponding time slot within the current frame has been figure 5-22. ac-link protocol sync bit_clk sdin slot ( 1 ) time slot "valid" bits 20.8us (48 khz) slot 1 slot 2 019 019 0 19 0 slot 3 slot 12 81.4 ns 12.288 mhz slot ( 2 ) "0" "0" "0" slot ( 12 ) ("1" = time slot contains valid pcm 19 codec read y end of previous a udio frame tag phase data phase functional description 5-146 82801BA ich2 and 82801BAm ich2-m datasheet assigned to a data stream and contains valid data. if a slot is tagged invalid with a zero in the corresponding bit position of slot 0, the ich2 stuffs the corresponding slot with zeros during that slot?s active time. within slot 0, the first bit is a valid frame bit (slot 0, bit 15) which flags the validity of the entire frame. if the valid frame bit is set to one, this indicates that the current frame contains at least one slot with valid data. when there is no transaction in progress, the ich2 deasserts the frame valid bit. note that after a write to slot 12, that slot always stays valid; therefore, the frame valid bit remains set. the next 12 bit positions of slot 0 (bits [14:3]) indicate which of the corresponding twelve time slots contain valid data. bits [1:0] of slot 0 are used as codec id bits to distinguish between separate codecs on the link. using the valid bits in the tag phase allows data streams of differing sample rates to be transmitted across the link at its fixed 48 khz frame rate. the codec can control the output sample rate of the ich2 using the slotreq bits as described in the ac?97 specification. output slot 1: command address port the command port is used to control features and monitor status of ac?97 functions including, but not limited to, mixer settings and power management. the control interface architecture supports up to 64 16-bit read/write registers, addressable on even byte boundaries. only the even registers (00h, 02h, etc.) are valid. output frame slot 1 communicates control register address and write/read command information. in the case of the split codec implementation, accesses to the codecs are differentiated by the driver using address offsets 00h?7fh for the primary codec and address offsets 80h?feh for the secondary codec. the differentiation on the link, however, is done via the codec id bits. see section for further details. output slot 2: command data port the command data port is used to deliver 16-bit control register write data in the event that the current command port operation is a write cycle as indicated in slot 1, bit 19. if the current command port operation is a read then the entire slot time stuffed with 0s by the ich2. bits [19:4] contain the write data. bits [3:0] are reserved and are stuffed with zeros. output slot 3: pcm playback left channel output frame slot 3 is the composite digital audio left playback stream. typically, this slot is composed of standard pcm (.wav) output samples digitally mixed by the host processor. the ich2 transmits sample streams of 16 bits and stuffs the remaining bits with zeros. data in output slots 3 and 4 from the ich2 should be duplicated by software if there is only a single channel out. output slot 4: pcm playback right channel output frame slot 4 is the composite digital audio right playback stream. typically, this slot is composed of standard pcm (.wav) output samples digitally mixed by the host processor. the ich2 transmits sample streams of 16 bits and stuffs the remaining bits with zeros. data in output slots 3 and 4 from the ich2 should be duplicated by software if there is only a single channel out. 82801BA ich2 and 82801BAm ich2-m datasheet 5-147 functional description output slot 5: modem codec output frame slot 5 contains modem dac data. the modem dac output supports 16 bit resolution. at boot time, if the modem codec is supported, the ac?97 controller driver determines the dac resolution. during normal runtime operation the ich2 stuffs trailing bit positions within this time slot with 0s. output slot 6: pcm playback center front channel when set up for 6 channel mode, this slot is used for the front center channel. the format is the same as slots 3. if not set up for 6 channel mode, this channel will always be stuffed with 0s by ich2. output slots 7?8: pcm playback left and right rear channels when set up for 4 or 6 channel modes, slots 7 and 8 are used for the rear left and right channels. the format for these two channels are the same as slots 3 and 4. output slot 9: playback subwoofer channel when set for 6 channel mode, this slot is used for the subwoofer. the format is the same as slots 3. if not set up for 6 channel mode, this channel will always be stuffed with 0s by ich2. output slots 10?11: reserved output frame slots 10?11 are reserved and are always stuffed with 0s by the ich2 ac?97 controller. output slot 12: i/o control the 16 bits of daa and gpio control (output) and status (input) have been directly assigned to bits on slot 12 to minimize latency of access to changing conditions. the value of the bits in this slot are the values written to the gpio control register at offset 54h and d4h (in the case of a secondary codec) in the modem codec i/o space. the following rules govern the usage of slot 12. 1. slot 12 is marked invalid by default on coming out of ac-link reset and will remain invalid until a register write to 54h/d4h. 2. a write to offset 54h/d4h in codec i/o space will cause the write data to be transmitted on slot 12 in the next frame, with slot 12 marked valid, and the address/data information to also be transmitted on slots 1 and 2. 3. after the first write to offset 54h/d4h, slot 12 remains valid for all following frames. the data transmitted on slot 12 is the data last written to offset 54h/d4h. any subsequent write to the register will cause the new data to be sent out on the next frame. 4. slot 12 will get invalidated after the following events: pci reset, ac'97 cold reset, warm reset, and hence a wake from s3, s4, or s5. slot 12 will remain invalid until the next write to offset 54h/d4h. functional description 5-148 82801BA ich2 and 82801BAm ich2-m datasheet ac-link input frame (sdin) there are two sdin lines on the ich2 for use with a primary and secondary codec. each sdin pin can have a codec attached. depending upon which codec (ac, mc, or amc) is attached, various slots will be valid or invalid. the data slots on the two inputs must be completely orthogonal (except for the tag slot 0), that is, no two data slots at the same location will be valid on both lines. this precludes the use of two similar codecs (e.g., two acs or mcs) which use the same time slots. the input frame data streams correspond to the multiplexed bundles of all digital input data targeting the ac?97 controller. as in the case for the output frame, each ac-link input frame consists of twelve time slots. a new audio input frame begins with a low-to-high transition of ac_sync. ac_sync is synchronous to the rising edge of bit_clk. on the immediately following falling edge of bit_clk, the receiver samples the assertion of ac_sync. this falling edge marks the time when both sides of ac-link are aware of the start of a new audio frame. on the next rising edge of bit_clk, the codec transitions sdin into the first bit position of slot 0 (codec ready bit). each new bit position is presented to ac-link on a rising edge of bit_clk and subsequently sampled by the ich2 on the following falling edge of bit_clk. this sequence ensures that data transitions and subsequent sample points for both incoming and outgoing data streams are time aligned. sdin data stream must follow the ac?97 specification and be msb justified with all non-valid bit positions (for assigned and/or unassigned time slots) stuffed with zeros. sdin data is sampled by the ich2 on the falling edge of bit_clk. input slot 0: tag phase input slot 0 consists of a codec ready bit (bit 15) and slot valid bits for each subsequent slot in the frame (bits [14:3]). the codec ready bit within slot 0 (bit 15) indicates whether the codec on the ac-link is ready for operation. if the codec ready bit in slot 0 is a zero, the codec is not ready for normal operation. when the ac-link codec ready bit is a 1, it indicates that the ac-link and codec control and status registers are in a fully operational state. the codec ready bits are visible through the global status register of the ich2. software must further probe the powerdown control/status register in the codec to determine exactly which subsections, if any, are ready. bits [14:3] in slot 0 indicate which slots of the input stream to the ich2 contain valid data, just as in the output frame. the remaining bits in this slot are stuffed with zeros. input slot 1: status address port / slot request bits the status port is used to monitor status of codec functions including, but not limited to, mixer settings and power management. slot 1 must echo the control register index, for historical reference, for the data to be returned in slot 2, assuming that slots 1 and 2 had been tagged valid by the codec in slot 0. for multiple sample rate output, the codec examines its sample rate control registers, the state of its fifos, and the incoming sdout tag bits at the beginning of each audio output frame to determine which slotreq bits to set active (low). slotreq bits asserted during the current audio input frame signal which output slots require data from the controller in the next audio output frame. for fixed 48 khz operation the slotreq bits are always set active (low) and a sample is transferred each frame. for multiple sample rate input, the tag bit for each input slot indicates whether valid data is present or not. 82801BA ich2 and 82801BAm ich2-m datasheet 5-149 functional description note: *slot 3 request and slot 4 request bits must be the same value, i.e. set or cleared in tandem. this is also true for the slot 7 and slot 8 request bits, as well as the slot 6 and slot 9 request bits. as shown in table 5-90 , slot 1 delivers codec control register read address and multiple sample rate slot request flags for all output slots of the controller. when a slot request bit is set by the codec, the controller returns data in that slot in the next output frame. slot request bits for slots 3 and 4 are always set or cleared in tandem (i.e., both are set or cleared). when set, the input slot 1 tag bit only pertains to status address port data from a previous read. slotreq bits are always valid independent of the slot 1 tag bit. input slot 2: status data port the status data port receives 16-bit control register read data. bit [19:4]: control register read data bit [3:0]: reserved. input slot 3: pcm record left channel input slot 3 is the left channel input of the codec. ich2 supports 16 bit sample resolution. samples transmitted to the ich2 must be in left/right channel order. input slot 4: pcm record right channel input slot 4 is the right channel input of the codec. the ich2 supports 16 bit sample resolution. samples transmitted to the ich2 must be in left/right channel order. input slot 5: modem line input slot 5 contains msb justified modem data. the ich2 supports 16 bit sample resolution. table 5-90. input slot 1 bit definitions bit description 19 reserved (set to zero) 18:12 control register index (stuffed with zeros if tagged invalid) 11 slot 3 request: pcm left channel* 10 slot 4 request: pcm right channel* 9 slot 5 request: modem line 1 8 slot 6 request: pcm center channel* 7 slot 7 request: pcm left surround* 6 slot 8 request: pcm right surround* 5 slot 9 request: pcm lfe channel* 4:2 slot request 10-12: not implemented 1:0 reserved (stuffed with zeros) functional description 5-150 82801BA ich2 and 82801BAm ich2-m datasheet input slot 6: optional dedicated microphone record data input slot 6 is a third pcm system input channel available for dedicated use by a microphone. this input channel supplements a true stereo output that enables more precise echo cancellation algorithm for speakerphone applications. the ich2 supports 16 bit resolution for slot 6 input. input slots 7-11: reserved input frame slots 7?11 are reserved for future use and should be stuffed with zeros by the codec, per the ac?97 specification. input slot 12: i/o status the status of the gpios configured as inputs are to be returned on this slot in every frame. the data returned on the latest frame is accessible to software by reading the register at offset 54h/d4h in the codec i/o space. only the 16 msbs are used to return gpi status. bit 0 of this slot indicates the gpi status. when a gpi changes state, this bit gets set for one frame by the codec. this bit can cause an interrupt to the processor if enabled via the global control register. reads from 54h/d4h are not transmitted across the link in slot 1 and 2. the data from the most recent slot 12 is returned on reads from offset 54h/d4h. register access in the ich2 implementation of the ac-link, up to two codecs can be connected to the sdout pin. the following mechanism is used to address the primary and secondary codecs individually. the primary device uses bit 19 of slot 1 as the direction bit to specify read or write. bits [18:12] of slot 1 are used for the register index. for i/o writes to the primary codec, the valid bits [14:13] for slots 1 and 2 must be set in slot 0, as shown in table 5-91 . slot 1 is used to transmit the register address and slot 2 is used to transmit data. for i/o reads to the primary codec, only slot 1 should be valid since only an address is transmitted. for i/o reads, only slot 1 valid bit is set; for i/o writes, both slots 1 and 2 valid bits are set. the secondary codec registers are accessed using slots 1 and 2 as described above, however the slot valid bits for slots 1 and 2 are marked invalid in slot 0 and the codec id bit 0 (bit 0 of slot 0) is set to 1. this allows the secondary codec to monitor the slot valid bits of slots 1and 2, and bit 0 of slot 0 to determine if the access is directed to the secondary codec. if the register access is targeted to the secondary codec, slot 1 and 2 will contain the address and data for the register access. since slots 1 and 2 are marked invalid, the primary codec will ignore these accesses. table 5-91. output tag slot 0 bit primary access example secondary access example description 15 1 1 frame valid 14 1 0 slot 1 valid, command address bit (primary codec only) 13 1 0 slot 2 valid, command data bit (primary codec only) 12:3 x x slot 3-12 valid 2 0 0 reserved 1:0 00 01 codec id (00 reserved for primary; 01 indicate secondary) 82801BA ich2 and 82801BAm ich2-m datasheet 5-151 functional description when accessing the codec registers, only one i/o cycle can be pending across the ac-link at any time. the ich2 implements write posting on i/o writes across the ac-link (i.e., writes across the link are indicated as complete before they are actually sent across the link). to prevent a second i/o write from occurring before the first one is complete, software must monitor the cas bit in the codec access semaphore register which indicates that a codec access is pending. once the cas bit is cleared, then another codec access (read or write) can go through. the exception is reads to offset 54h/d4h (slot 12) which are returned immediately with the most recently received slot 12 data. writes to offset 54h and d4h (primary and secondary codecs), get transmitted across the ac-link in slots 1 and 2 as a normal register access. slot 12 is also updated immediately to reflect the data being written. the controller will not issue back-to-back reads. it must get a response to the first read before issuing a second. in addition, codec reads and writes are only executed once across the link, and are not repeated. 5.18.2 ac-link low power mode the ac-link signals can be placed in a low power mode. when the ac?97 powerdown register (26h), is programmed to the appropriate value, both bit_clk and sdin will be brought to and held at a logic low voltage level. bit_clk and sdin transition low immediately following a write to the powerdown register (26h) with pr4. when the ac?97 controller driver is at the point where it is ready to program the ac-link into its low power mode, slots 1 and 2 are assumed to be the only valid stream in the audio output frame. the ac?97 controller also drives ac_sync, and sdout low after programming ac?97 to this low power, halted mode. once the codec has been instructed to halt bit_clk, a special wake up protocol must be used to bring the ac-link to the active mode since normal output and input frames can not be communicated in the absence of bit_clk. once in a low power mode, the ich2 provides three methods for waking up the ac-link; external wake event, cold reset and warm reset. note: before entering any low power mode where the link interface to the codec is expected to be powered down while the rest of the system is awake, the software must set the "shut off" bit in the control register. figure 5-23. ac-link powerdown timing sdout tag sync bit_clk write to 0x20 data pr4 slot 12 prev. frame tag slot 12 prev. frame sdin note: bit_clk not to scale functional description 5-152 82801BA ich2 and 82801BAm ich2-m datasheet external wake event codecs can signal the controller to wake the ac-link and wake the system using sdin. the minimum sdin wake up pulse width is 1 us. the rising edge of sdin[0] or sdin[1] causes the ich2 to sequence through an ac-link warm reset and set the ac97_sts bit in the gpe0_sts register to wake the system. the primary codec must wait to sample ac_sync high and low before restarting bit_clk as diagrammed in figure 5-24 . the codec that signaled the wake event must keep its sdin high until it has sampled ac_sync having gone high, and then low. the ac-link protocol provides for a cold reset and a warm reset. the type of reset used depends on the system?s current power down state. unless a cold or register reset (a write to the reset register in the codec) is performed, wherein the ac?97 codec registers are initialized to their default values, registers are required to keep state during all power down modes. once powered down, activation of the ac-link via re-assertion of the ac_sync signal must not occur for a minimum of 4 audio frame times following the frame in which the power down was triggered. when ac-link powers up, it indicates readiness via the codec ready bit. 5.18.3 ac?97 cold reset a cold reset is achieved by asserting ac_rst# for 1 us. by driving ac_rst# low, bit_clk, and sdout will be activated and all codec registers will be initialized to their default power on reset values. ac_rst# is an asynchronous ac?97 input to the codec. 5.18.4 ac?97 warm reset a warm reset re-activates the ac-link without altering the current codec register values. a warm reset is signaled by driving ac_sync high for a minimum of 1 us in the absence of bit_clk. within normal frames, ac_sync is a synchronous ac?97 input to the codec. however, in the absence of bit_clk, ac_sync is treated as an asynchronous input to the codec used in the generation of a warm reset. the codec must not respond with the activation of bit_clk until ac_sync has been sampled low again by the codec. this will prevent the false detection of a new frame. note: on receipt of wake up signalling from the codec, the digital controller will issue an interrupt if enabled. software will then have to issue a warm or cold reset to the codec by setting the appropriate bit in the global control register. figure 5-24. sdin wake signaling sdout tag sync bit_clk write to 0x20 data pr4 slot 12 prev. frame tag slot 12 prev. frame sdin tag slot 1 slot 2 power down frame wake event sleep state new audio frame tag slot 1 slot 2 82801BA ich2 and 82801BAm ich2-m datasheet 5-153 functional description 5.18.5 system reset table 5-92 indicates the states of the link during various system reset and sleep conditions. note: 1. ich2 core well outputs are used as strapping options for the ich2. they are sampled during system reset. these signals may have weak pull-ups/put-downs. the ich2 outputs are driven to the appropriate level prior to ac_rst# being deasserted, preventing a codec from entering test mode. straps are tied to the core well to prevent leakage during a suspend state. 2. the pull-down resistors on these signals are only enabled when the ac-link shut off bit in the ac?97 global control register is set to 1. all other times, the pull-down resistor is disabled. 3. ac_rst# will be held low during s3?s5. it cannot be programmed high during a suspend state. 4. bit_clk and sdin[1:0] are driven low by the codecs during normal states. if the codec is powered during suspend states, it holds these signals low. however, if the codec is not present or not powered in suspend, external pull-down resistors are required. the transition of ac_rst# to the deasserted state only occurs under driver control. in the s1sleep state, the state of the ac_rst# signal is controlled by the ac?97 cold reset# bit (bit 1) in the global control register. ac_rst# will be asserted (low) by the ich2 under the following conditions: ? rsmrst# (system reset, including the a reset of the resume well and pcirst#) ? mechanical power up (causes pcirst#) ? write to cf9h hard reset (causes pcirst#) ? transition to s3/s4/s5 sleep states (causes pcirst#) ? write to ac?97 cold reset# bit in the global control register. hardware will never deassert ac_rst# (i.e., never deasserts the cold reset# bit) automatically. only software can deassert the cold reset# bit and, hence, the ac_rst# signal. this bit, while it resides in the core well, remains cleared upon return from s3/s4/s5 sleep states. the ac_rst# pin remains actively driven from the resume well as indicated. table 5-92. ac-link state during pcirst# signal power plane i/o during pcirst#/ after pcirst#/ s1 s3 s4/s5 ac_rst# resume 3 output low low cold reset bit (hi) low low ac_sdout core 1 output low running low low low ac_sync core 1 output low running low low low bit_clk core input driven by codec running low 2,4 low 2,4 low 2,4 sdin[1:0] resume input driven by codec running low 2,4 low 2,4 low 2,4 functional description 5-154 82801BA ich2 and 82801BAm ich2-m datasheet 5.19 firmware hub interface this section describes the memory cycle type to be used on the firmware hub (fwh) interface. below are the various types of cycles that are supported by the product. 5.19.1 field definitions start this one clock field indicates the start of a cycle. it is valid on the last clock that lframe# is sampled low. the two start fields that are used for the cycle are shown in the table below. if the start field that is sampled is not one of these values, then the cycle attempted is not a fwh memory cycle. it may be a valid memory cycle that the fwh component may wish to decode (i.e., it may be of the lpc memory cycle variety). idsel (device select) this one clock field is used to indicate which fwh component is being selected. the four bits transmitted over ad[3:0] during this clock are compared with values strapped onto pins on the fwh component. if there is a match, the fwh component will continue to decode the cycle to determine which bytes are requested on a read or which bytes to update on a write. if there is not a match, the fwh component may discard the rest of the cycle and go into a standby power state. msize (memory size) the value ?0000b? is sent in this field. a value of ?0000b? corresponds to a single byte transfer. other encodings of this field are reserved for future use. maddr (memory address) this is a 7-clock field that provides a 28 bit memory address. this allows for up to 256 mb per memory device, for a total of a 4 gb addressable space. the address is transferred with the most significant nibble first. sync the sync protocol is the same as described in the lpc specification. tar the tar fields are the same as described in the lpc specification. refer to this specification for further details. cycle type comment fwh memory read new chip select and addressing are used. fwh memory write new chip select and addressing are used. ad[3:0] indication 1101 fwh memory read 1110 fwh memory write 82801BA ich2 and 82801BAm ich2-m datasheet 5-155 functional description 5.19.2 protocol the fwh memory cycles use a sequence of events that start with a start field (lframe# active with appropriate ad[3:0] combination) and end with the data transfer. the following sections describe the cycles in detail. preamble the initiation of the fwh memory cycles is shown in figure 5-25 . the fwh memory transaction begins with lframe# going low and a start field driven on ad[3:0]. for fwh memory read cycles, the start field must be ?1101b?; for fwh memory write cycles, the start field must be ?1110b?. following the start field is the idsel field. this field acts like a chip select in that it indicates which device should respond to the current transaction. the next seven clocks are the 28- bit address from where to begin reading in the selected device. next, an msize value of 0 indicates the master is requesting a single byte. read cycle (single byte) for read cycles, after the pre-amble (described above), the host drives a tar field to give ownership of the bus to the fwh. after the second clock of the tar phase, the target device assumes the bus and begins driving sync values. when it is ready, it drives the low nibble, then the high nibble of data, followed by a tar to give control back to the host. figure 5-26 shows a device that requires 3 sync clocks to access data. since the access time can begin once the address phase has been completed, the two clocks of the tar phase can be considered as part of the access time of the part. for example, a device with a 120 ns access time could assert ?0101b? for clocks 1 and 2 of the sync phase and ?0000b? for the last clock of the sync phase. this would be equivalent to 5 clocks worth of access time if the device started that access at the conclusion of the preamble phase. once sync is achieved, the device returns the data in two clocks and gives ownership of the bus back to the host with a tar phase. figure 5-25. fwh memory cycle preamble t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 clk frame# ad[3:0] idsel start msize 28 bit address figure 5-26. single byte read fh d t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 clk frame# ad[3:0] tar preamble t12 t13 sync d_lo d_hi tar functional description 5-156 82801BA ich2 and 82801BAm ich2-m datasheet write cycles (single byte) all devices that support fwh memory write cycles must support single byte writes. fwh memory write cycles use the same preamble as fwh memory read cycles that is described above. figure 5-27 shows an fwh memory write cycle where a single byte is transferred. the master asserts an msize value of 0. after the address has been transferred, the 2 clock data phase begins. following the data phase, bus ownership is transferred to the fwh component with a tar cycle. following the tar phase, the device must assert a sync value of ?0000b? (ready) or ?1010b? (error) indicating the data has been received. bus ownership is then given back to the master with another tar phase. fwh memory writes only allow one clock for the sync phase. the tar + sync + tar phases at the end of fwh memory write cycles must be exactly 5 clocks. error reporting there is no error reporting over the fwh interface for fwh memory cycles. if an error occurs (e.g., an address out of range or an unsupported memory size), the cycle will continue from the host unabated. this is because these errors are the result of illegal programming, and there is no efficient error reporting method that can be done to counter the programming error. therefore, the fwh component must not report the error conditions over the fwh interface. it must only report wait states and the ?ready? condition. it may choose to log the error internally to be debugged, but it must not signal an error through the fwh interface itself figure 5-27. single byte write t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 clk frame# ad[3:0] tar preamble sync d_lo d_hi tar 82801BA ich2 and 82801BAm ich2-m datasheet 6-1 register and memory mapping register and memory mapping 6 the ich2 contains registers that are located in the processor?s i/o space and memory space and sets of pci configuration registers that are located in pci configuration space. this chapter describes the ich2 i/o and memory maps at the register-set level. register access is also described. register-level address maps and individual register bit descriptions are provided in the following chapters. the following notations and definitions are used in the register/instruction description chapters. ro read only. in some cases, if a register is read only, writes to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. wo write only. in some cases, if a register is write only, reads to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. r/w read/write. a register with this attribute can be read and written. r/wc read/write clear. a register bit with this attribute can be read and written. however, a write of 1 clears (sets to 0) the corresponding bit and a write of 0 has no effect. default when ich2 is reset, it sets its registers to predetermined default states. the default state represents the minimum functionality feature set required to successfully bring up the system. hence, it does not represent the optimal system configuration. it is the responsibility of the system initialization software to determine configuration, operating parameters, and optional system features that are applicable, and to program the ich2 registers accordingly. bold register bits that are highlighted in bold text indicate that the bit is implemented in the ich2. register bits that are not implemented or are rewired will remain in plain text. 6.1 pci devices and functions the ich2 incorporates a variety of pci functions as shown in table 6-1 . these functions are divided into three logical devices (b0:d30, b0:d31 and b1:d8). d30 is the hub interface-to-pci bridge, d31 contains the pci-to-lpc bridge, ide controller, usb controllers, smbus controller and the ac?97 audio and model controller functions. b1:d8 is the integrated lan controller. note: from a software perspective, the integrated lan controller resides on the ich2?s external pci bus (see section 5.1.2 ). this is typically bus 1, but may be assigned a different number depending on system configuration. if a particular system platform does not want to support any one of device 31?s functions 1?6, they can individually be disabled. the integrated lan controller will be disabled if no platform lan connect component is detected (see section 5.2, ?lan controller (b1:d8:f0)? on page 5-6 ). when a function is disabled, it does not appear at all to the software. a disabled function will not respond to any register reads or writes. this is intended to prevent software from thinking that a function is present (and reporting it to the end-user). register and memory mapping 6-2 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. the pci to lpc bridge contains registers that control lpc, power management, system management, gpio, processor interface, rtc, interrupts, timers, dma. 6.2 pci configuration map each pci function on the ich2 has a set of pci configuration registers. the register address map tables for these register sets are included at the beginning of the chapter for the particular function. configuration space registers are accessed through configuration cycles on the pci bus by the host bridge using configuration mechanism #1 detailed in the pci 2.1 specification. some of the pci registers contain reserved bits. software must deal correctly with fields that are reserved. on reads, software must use appropriate masks to extract the defined bits and not rely on reserved bits being any particular value. on writes, software must ensure that the values of reserved bit positions are preserved. that is, the values of reserved bit positions must first be read, merged with the new values for other bit positions and then written back. note the software does not need to perform read, merge, write operation for the configuration address register. in addition to reserved bits within a register, the configuration space contains reserved locations. software should not write to reserved pci configuration locations in the device-specific region (above address offset 3fh). 6.3 i/o map the i/o map is divided into fixed and variable address ranges. fixed ranges cannot be moved. in some cases they can be disabled. variable ranges can be moved and can also be disabled. table 6-1. pci devices and functions bus:device:function function description bus 0:device 30:function 0 hub interface to pci bridge bus 0:device 31:function 0 pci to lpc bridge 1 bus 0:device 31:function 1 ide controller bus 0:device 31:function 2 usb controller #1 bus 0:device 31:function 3 smbus controller bus 0:device 31:function 4 usb controller #2 bus 0:device 31:function 5 ac?97 audio controller bus 0:device 31:function 6 ac?97 modem controller bus 1:device 8:function 0 lan controller 82801BA ich2 and 82801BAm ich2-m datasheet 6-3 register and memory mapping 6.3.1 fixed i/o address ranges table 6-2 shows the fixed i/o decode ranges from the processor perspective. note that for each i/o range, there may be a separate behavior for reads and writes. the hub interface cycles that go to target ranges that are marked as ?reserved? are not decoded by the ich2; they are passed to pci. if a pci master targets one of the fixed i/o target ranges, it will be positively decoded by the ich2 in medium speed. refer to table a-1 for a complete list of all fixed i/o registers. address ranges that are not listed or marked ?reserved? are not decoded by the ich2 (unless assigned to one of the variable ranges). table 6-2. fixed i/o ranges decoded by ich2 i/o address read target write target internal unit 00h?08h dma controller dma controller dma 09h?0eh reserved dma controller dma 0fh dma controller dma controller dma 10h?18h dma controller dma controller dma 19h?1eh reserved dma controller dma 1fh dma controller dma controller dma 20h?21h interrupt controller interrupt controller interrupt 24h?25h interrupt controller interrupt controller interrupt 28h?29h interrupt controller interrupt controller interrupt 2ch?2dh interrupt controller interrupt controller interrupt 2eh?2fh lpc sio lpc sio forwarded to lpc 30h?31h interrupt controller interrupt controller interrupt 34h?35h interrupt controller interrupt controller interrupt 38h?39h interrupt controller interrupt controller interrupt 3ch?3dh interrupt controller interrupt controller interrupt 40h?42h timer/counter timer/counter pit (8254) 43h reserved timer/counter pit 4e?4f lpc sio lpc sio forwarded to lpc 50h?52h timer/counter timer/counter pit 53h reserved timer/counter pit 60h microcontroller microcontroller forwarded to lpc 61h nmi controller nmi controller processor i/f 62h microcontroller microcontroller forwarded to lpc 63h nmi controller nmi controller processor i/f 64h microcontroller microcontroller forwarded to lpc 65h nmi controller nmi controller processor i/f 66h microcontroller microcontroller forwarded to lpc 67h nmi controller nmi controller processor i/f 70h reserved 5 nmi and rtc controller rtc 71h rtc controller rtc controller rtc 72h rtc controller nmi and rtc controller rtc 73h rtc controller rtc controller rtc 74h rtc controller nmi and rtc controller rtc register and memory mapping 6-4 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. only if ide standard i/o space is enabled for primary drive. otherwise, the target is pci. 2. only if ide standard i/o space is enabled for secondary drive. otherwise, the target is pci. 3. if pos_dec_en bit is enabled, reads from f0h will not be decoded by the ich2. if pos_dec_en is not enabled, reads from f0h will forward to lpc. 75h rtc controller rtc controller rtc 76h rtc controller nmi and rtc controller rtc 77h rtc controller rtc controller rtc 80h dma controller dma controller and lpc or pci dma 81h?83h dma controller dma controller dma 84h?86h dma controller dma controller and lpc or pci dma 87h dma controller dma controller dma 88h dma controller dma controller and lpc or pci dma 89h?8bh dma controller dma controller dma 8ch?8eh dma controller dma controller and lpc or pci dma 08fh dma controller dma controller dma 90h?91h dma controller dma controller dma 92h reset generator reset generator processor i/f 93h?9fh dma controller dma controller dma a0h?a1h interrupt controller interrupt controller interrupt a4h?a5h interrupt controller interrupt controller interrupt a8h?a9h interrupt controller interrupt controller interrupt ach?adh interrupt controller interrupt controller interrupt b0h?b1h interrupt controller interrupt controller interrupt b2h?b3h power management power management power management b4h?b5h interrupt controller interrupt controller interrupt b8h?b9h interrupt controller interrupt controller interrupt bch?bdh interrupt controller interrupt controller interrupt c0h?d1h dma controller dma controller dma d2h?ddh reserved dma controller dma deh?dfh dma controller dma controller dma f0h see note 3 ferr#/ignne# / interrupt controller processor interface 170h?177h ide controller 2 ide controller 1 forwarded to ide 1f0h?1f7h ide controller 1 ide controller 2 forwarded to ide 376h ide controller 2 ide controller 1 forwarded to ide 3f6h ide controller 1 ide controller 2 forwarded to ide 4d0h?4d1h interrupt controller interrupt controller interrupt cf9h reset generator reset generator processor interface table 6-2. fixed i/o ranges decoded by ich2 (continued) i/o address read target write target internal unit 82801BA ich2 and 82801BAm ich2-m datasheet 6-5 register and memory mapping 6.3.2 variable i/o decode ranges table 6-3 shows the variable i/o decode ranges. they are set using base address registers (bars) or other configuration bits in the various pci configuration spaces. the pnp software (pci or acpi) can use their configuration mechanisms to set and adjust these values. when a cycle is detected on the hub interface, the ich2 positively decodes the cycle. if the response is on the behalf of an lpc device, ich2 will forward the cycle to the lpc interface. refer to table a-2 for a complete list of all variable i/o registers. warning: the variable i/o ranges should not be set to conflict with the fixed i/o ranges. unpredictable results if the configuration software allows conflicts to occur. the ich2 does not perform any checks for conflicts. table 6-3. variable i/o decode ranges range name mappable size (bytes) target acpi anywhere in 64 kb i/o space 64 power management ide anywhere in 64 kb i/o space 16 ide unit usb #1 anywhere in 64 kb i/o space 32 usb unit 1 smbus anywhere in 64 kb i/o space 16 smb unit ac?97 audio mixer anywhere in 64 kb i/o space 256 ac?97 unit ac?97 bus master anywhere in 64 kb i/o space 64 ac?97 unit ac?97 modem mixer anywhere in 64 kb i/o space 256 ac?97 unit tco 96 bytes above acpi base 32 tco unit gpio anywhere in 64 kb i/o space 64 gpio unit parallel port 3 ranges in 64 kb i/o space 8 lpc peripheral serial port 1 8 ranges in 64 kb i/o space 8 lpc peripheral serial port 2 8 ranges in 64 kb i/o space 8 lpc peripheral floppy disk controller 2 ranges in 64 kb i/o space 8 lpc peripheral midi 4 ranges in 64 kb i/o space 2 lpc peripheral mss 4 ranges in 64 kb i/o space 8 lpc peripheral soundblaster 2 ranges in 64 kb i/o space 32 lpc peripheral lan anywhere in 64 kb i/o space 64 lan unit usb #2 anywhere in 64 kb i/o space 32 usb unit 2 lpc generic 1 anywhere in 64 kb i/o space 128 lpc peripheral lpc generic 2 anywhere in 64 kb i/o space 16 lpc peripheral monitors 4:7 anywhere in 64 kb i/o space 16 lpc peripheral or trap on pci register and memory mapping 6-6 82801BA ich2 and 82801BAm ich2-m datasheet 6.4 memory map table 6-4 shows (from the processor perspective) the memory ranges that the ich2 decodes. cycles that arrive from the mch will first be driven out on pci. the ich2 may then claim the cycle for it to be forwarded to lpc or claimed by the internal apic. if subtractive decode is enabled, the cycle can be forwarded to lpc. pci cycles generated by an external pci master will be positively decoded unless it falls in the pci-pci bridge forwarding range (those addresses are reserved for pci peer-to-peer traffic). if the cycle is not in the i/o apic or lpc ranges, it will be forwarded up the hub interface to the host controller. table 6-4. memory decode ranges from processor perspective memory range target dependency/comments 0000 0000h?000d ffffh 0010 0000?tom (top of memory) main memory tom registers in host controller 000e 0000h?000f ffffh fwh bit 7 in fwh decode enable register is set fec0 0000h?fec0 0100h i/o apic inside ich2 ffc0 0000h?ffc7 ffffh ff80 0000h?ff87 ffffh fwh bit 0 in fwh decode enable register ffc8 0000h?ffcf ffffh ff88 0000h?ff8f ffffh fwh bit 1 in fwh decode enable register ffd0 0000h?ffd7 ffffh ff90 0000h?ff97 ffffh fwh bit 2 in fwh decode enable register is set ffd8 0000h?ffdf ffffh ff98 0000h?ff9f ffffh fwh bit 3 in fwh decode enable register is set ffe0 000h?ffe7 ffffh ffa0 0000h?ffa7 ffffh fwh bit 4 in fwh decode enable register is set ffe8 0000h?ffef ffffh ffa8 0000h?ffaf ffffh fwh bit 5 in fwh decode enable register is set fff0 0000h?fff7 ffffh ffb0 0000h?ffb7 ffffh fwh bit 6 in fwh decode enable register is set. fff8 0000h?ffff ffffh ffb8 0000h?ffbf ffffh fwh always enabled. the top two 64 kb blocks of this range can be swapped as described in section 6.4.1 . ff70 0000h?ff7f ffffh ff30 0000h?ff3f ffffh fwh bit 3 in fwh decode enable 2 register is set ff60 0000h?ff6f ffffh ff20 0000h?ff2f ffffh fwh bit 2 in fwh decode enable 2 register is set ff50 0000h?ff5f ffffh ff10 0000h?ff1f ffffh fwh bit 1 in fwh decode enable 2 register is set ff40 0000h?ff4f ffffh ff00 0000h?ff0f ffffh fwh bit 0 in fwh decode enable 2 register is set anywhere in 4 gb range d110 lan controller enable via bar in device 29:function 0 (d110 lan controller) all other pci none 82801BA ich2 and 82801BAm ich2-m datasheet 6-7 register and memory mapping 6.4.1 boot-block update scheme the ich2 supports a ?top-block swap? mode that has the ich2 swap the top block in the fwh (the boot block) with another location. this allows for safe update of the boot block (even if a power failure occurs). when the ?top-swap? enable bit is set, the ich2 will invert a16 for cycles targeting fwh bios space. when this bit is 0, the ich2 will not invert a16. this bit is automatically set to 0 by rtcrst#, but not by pcirst#. the scheme is based on the concept that the top block is reserved as the ?boot? block, and the block immediately below the top block is reserved for doing boot-block updates. the algorithm is: 1. software copies the top block to the block immediately below the top 2. software checks that the copied block is correct. this could be done by performing a checksum calculation. 3. software sets the ?top-block swap? bit. this inverts a16 for cycles going to the fwh. processor access to ffff_0000 through ffff_ffff are directed to ffff_0000 through fffe_ffff in the fwh. processor accesses to fffe_0000 through fffe_ffff are directed to ffff_0000 through ffff_ffff. 4. software erases the top block 5. software writes the new top block 6. software checks the new top block 7. software clears the top-block swap bit if a power failure occurs at any point after step 3, the system will be able to boot from the copy of the boot block that is stored in the block below the top. this is because the top-swap bit is backed in the rtc well. note: the top-block swap mode may be forced by an external strapping option (see section 2.20.1 ). when top-block swap mode is forced in this manner, the top-swap bit cannot be cleared by software. a re-boot with the strap removed will be required to exit a forced top-block swap mode. note: top-block swap mode only affects accesses to the fwh bios space, not feature space. note: the top block swap mode has no effect on accesses below fffe_0000. register and memory mapping 6-8 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank. 82801BA ich2 and 82801BAm ich2-m datasheet 7-1 lan controller registers (b1:d8:f0) lan controller registers (b1:d8:f0) 7 the ich2 integrated lan controller appears to reside at pci device 8, function 0 on the secondary side of the ich2?s virtual pci-to-pci bridge (see table 5.1.2 ). this is typically bus 1, but may be assigned a different number depending upon system configuration. the lan controller acts as both a master and a slave on the pci bus. as a master, the lan controller interacts with the system main memory to access data for transmission or deposit received data. as a slave, some of the lan controller?s control structures are accessed by the host processor to read or write information to the on-chip registers. the processor also provides the lan controller with the necessary commands and pointers that allow it to process receive and transmit data. 7.1 pci configuration registers (b1:d8:f0) note: registers that are not shown should be treated as reserved (see section 6.2 for details). . note: refer to the specification update for the value of the revision id register. table 7-1. pci configuration map (lan controller?b1:d8:f0) offset mnemonic register name/function default type 00?01h vid vendor id 8086h ro 02?03h did device id 2449h ro 04?05h pcicmd pci device command register 0000h r/w 06?07h pcists pci device status register 0290h r/w 08h revid revision id note 1 ro 0ah scc sub class code 00h ro 0bh bcc base class code 02h ro 0dh pmlt pci master latency timer 00h r/w 0eh headtyp header type 00h ro 10?13h csr_mem_base csr memory-mapped base address 0008h r/w 14?17h csr_io_base csr i/o-mapped base address 0001h r/w 2c?2dh svid subsystem vendor id 0000h ro 2e?2fh sid subsystem id 0000h ro 34h cap_ptr capabilities pointer dch ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin 01h ro 3eh min_gnt minimum grant 08h ro 3fh max_lat maximum latency 38h ro dch cap_id capability id 01h ro ddh nxt_ptr next item pointer 00h ro de?dfh pm_cap power management capabilities fe21h (ich2) 7e21 (ich2-m) ro e0?e1h pmcsr power management control/status 0000h r/w e3h data data 00h ro lan controller registers (b1:d8:f0) 7-2 82801BA ich2 and 82801BAm ich2-m datasheet 7.1.1 vid?vendor id register (lan controller?b1:d8:f0) offset address: 00?01h attribute: ro default value: 8086h size: 16 bits 7.1.2 did?device id register (lan controller?b1:d8:f0) offset address: 02?03h attribute: ro default value: 2449h size: 16 bits 7.1.3 pcicmd?pci command register (lan controller?b1:d8:f0) offset address: 04?05h attribute: ro, r/w default value: 0000h size: 16 bits bit description 15:0 vendor identification number. this is a 16-bit value assigned to intel. bit description 15:0 device identification number. this is a 16 bit value assigned to the ich2 integrated lan controller. bit description 15:10 reserved. 9 fast back to back enable (fbe ) ?ro. hardwired to 0. the integrated lan controller will not run fast back-to-back pci cycles. 8 serr# enable (serr_en)? r/w. 1 = enable. allow serr# to be generated. 0 = disable. 7 wait cycle control (wcc)?ro. hardwired to 0. not implemented. 6 parity error response (per) ?r/w 1 = the integrated lan controller will take normal action when a pci parity error is detected. the generation of parity is also enabled on the hub interface. 0 = the lan controller will ignore pci parity errors. 5 vga palette snoop (vps)?ro. hardwired to 0. not implemented. 4 memory write and invalidate enable (mwie) ?r/w. 0 = disable. the lan controller will not use the memory write and invalidate command. 1 = enable. 3 special cycle enable (sce)?ro. hardwired to 0. the lan controller ignores special cycles. 2 bus master enable (bme) ?r/w. 1 = enable. the ich2?s integrated may function as a pci bus master. 0 = disable. 1 memory space enable (mse) ?r/w. 1 = enable. the ich2?s integrated lan controller will respond to the memory space accesses. 0 = disable. 0 i/o space enable (ioe) ?r/w. 1 = enable. the ich2?s integrated lan controller will respond to the i/o space accesses. 0 = disable. 82801BA ich2 and 82801BAm ich2-m datasheet 7-3 lan controller registers (b1:d8:f0) 7.1.4 pcists?pci status register (lan controller?b1:d8:f0) offset address: 06?07h attribute: ro, r/wc default value: 0290h size: 16 bits 7.1.5 revid?revision id register (lan controller?b1:d8:f0) offset address: 08h attribute: ro default value: 00h size: 8 bits bit description 15 detected parity error (dpe) ?r/wc. 1 = the ich2?s integrated lan controller has detected a parity error on the pci bus (will be set even if parity error response is disabled in the pci command register). 0 = this bit is cleared by writing a 1 to the bit location. 14 signaled system error (sse) ? r/wc. 1 = the ich2?s integrated lan controller has asserted serr#. (serr# can be routed to cause nmi, smi# or interrupt. 0 = this bit is cleared by writing a 1 to the bit location. 13 master abort status (rma) ?r/wc. 1 = the ich2?s integrated lan controller (as a pci master) has generated a master abort. 0 = this bit is cleared by writing a 1 to the bit location. 12 received target abort (rta) ?r/wc. 1 = the ich2?s integrated lan controller (as a pci master) has received a target abort. 0 = this bit is cleared by writing a 1 to the bit location. 11 signaled target abort (sta)?ro. hardwired to 0. the device will never signal target abort. 10:9 devsel# timing status (dev_sts)?ro. 01h = medium timing. 8 data parity error detected (dped) ?r/wc. 1 = all of the following three conditions have been met: 1.the lan controller is acting as bus master 2.the lan controller has asserted perr# (for reads) or detected perr# asserted (for writes) 3.the parity error response bit in the lan controller?s pci command register is set. 0 = this bit is cleared by writing a 1 to the bit location. 7 fast back to back (fb2b)?ro. hardwired to 1. the device can accept fast back-to-back transactions. 6 user definable features (udf)?ro. hardwired to 0. not implemented. 5 66 mhz capable (66mhz_cap)?ro. hardwired to 0. the device does not support 66mhz pci. 4 capabilities list (cap_list) ?ro. 1 = the eeprom indicates that the integrated lan controller supports pci power management. 0 = the eeprom indicates that the integrated lan controller does not support pci power management. 3:0 reserved. bit description 7:0 revision identification number. 8-bit value that indicates the revision number for the integrated lan controller. the three least significant bits in this register may be overridden by the id and rev id fields in the eeprom. lan controller registers (b1:d8:f0) 7-4 82801BA ich2 and 82801BAm ich2-m datasheet 7.1.6 scc?sub-class code register (lan controller?b1:d8:f0) offset address: 0ah attribute: ro default value: 00h size: 8 bits 7.1.7 bcc?base-class code register (lan controller?b1:d8:f0) offset address: 0bh attribute: ro default value: 02h size: 8 bits 7.1.8 cls?cache line size register (lan controller?b1:d8:f0) offset address: 0ch attribute: rw default value: 00h size: 8 bits 7.1.9 pmlt?pci master latency timer register (lan controller?b1:d8:f0) offset address: 0dh attribute: rw default value: 00h size: 8 bits bit description 7:0 sub-class code. 8-bit value that specifies the sub-class of the device as an ethernet controller. bit description 7:0 base class code. 8-bit value that specifies the base class of the device as a network controller. bit description 7:5 reserved. 4:3 cache line size (cls) ?rw. 00 = memory write and invalidate (mwi) command will not be used by the integrated lan controller. 01 = mwi command will be used with cache line size set to 8 dwords (only set if a value of 08h is written to this register). 10 = mwi command will be used with cache line size set to 16 dwords (only set if a value of 10h is written to this register). 11 = invalid. mwi command will not be used. 2:0 reserved. bit description 7:3 master latency timer count (mltc) ?rw. defines the number of pci clock cycles that the integrated lan controller may own the bus while acting as bus master. 2:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 7-5 lan controller registers (b1:d8:f0) 7.1.10 headtyp?header type register (lan controller?b1:d8:f0) offset address: 0eh attribute: ro default value: 00h size: 8 bits 7.1.11 csr_mem_base csr?memory-mapped base address register (lan controller?b1:d8:f0) offset address: 10?13h attribute: r/w, ro default value: 0000 0008h size: 32 bits note: the ich2?s integrated lan controller requires one bar for memory mapping. software determines which bar (memory or i/o) is used to access the lan controller?s csr registers. 7.1.12 csr_io_base?csr i/o-mapped base address register (lan controller?b1:d8:f0) offset address: 14?17h attribute: r/w default value: 0000 0001h size: 32 bits note: the ich2?s integrated lan controller requires one bar for memory mapping. software determines which bar (memory or i/o) is used to access the lan controller?s csr registers. bit description 7 multi-function device ?ro. hardwired to 0 to indicate a single function device. 6:0 header type ?ro. 7-bit field identifies the header layout of the configuration space as an ethernet controller. bit description 31:12 base address ?r/w. upper 20 bits of the base address provides 4 kb of memory-mapped space for the lan controller?s control/status registers. 11:4 reserved. 3 pre-fetchable?ro. hardwired to 0 to indicate that this is not a pre-fetchable memory-mapped address range. 2:1 type?ro. hardwired to 00b to indicate the memory-mapped address range may be located anywhere in 32-bit address space. 0 memory-space indicator?ro. hardwired to 0 to indicate that this base address maps to memory space. bit description 31:16 reserved. 15:6 base address ?r/w. provides 64 bytes of i/o-mapped address space for the lan controller?s control/status registers. 5:1 reserved. 0 i/o space indicator?ro. hardwired to 1 to indicate that this base address maps to i/o space. lan controller registers (b1:d8:f0) 7-6 82801BA ich2 and 82801BAm ich2-m datasheet 7.1.13 svid?subsystem vendor id (lan controller?b1:d8:f0) offset address: 2c?2d attribute: ro default value: 0000h size: 16 bits 7.1.14 sid?subsystem id (lan controller?b1:d8:f0) offset address: 2e?2fh attribute: ro default value: 0000h size: 16 bits note: the ich2?s integrated lan controller provides support for configureable subsystem id and subsystem vendor id fields. after reset, the lan controller automatically reads addresses ah through ch of the eeprom. the lan controller checks bits 15:13 in the eeprom word ah, and functions according to table 7-2 . 7.1.15 cap_ptr?capabilities pointer (lan controller?b1:d8:f0) offset address: 34h attribute: ro default value: dch size: 8 bits bit description 15:0 subsystem vendor id?ro. bit description 15:0 subsystem id?ro. table 7-2. configuration of subsystem id and subsystem vendor id via eeprom bits 15:14 bit 13 device id vendor id revision id subsystem id subsystem vendor id 11b, 10b, 00b x 2449h 8086h 00h 0000h 0000h 01b 0b 2449h 8086h 00h word bh word ch 01b 1b word bh word ch word ah, bits 10:8 word bh word ch bit description 7:0 capabilities pointer (cap_ptr) ?ro. hardwired to dch to indicate the offset within configuration space for the location of the power management registers. 82801BA ich2 and 82801BAm ich2-m datasheet 7-7 lan controller registers (b1:d8:f0) 7.1.16 int_ln?interrupt line register (lan controller?b1:d8:f0) offset address: 3ch attribute: r/w default value: 00h size: 8 bits 7.1.17 int_pn?interrupt pin register (lan controller?b1:d8:f0) offset address: 3dh attribute: ro default value: 01h size: 8 bits 7.1.18 min_gnt?minimum grant register (lan controller?b1:d8:f0) offset address: 3eh attribute: ro default value: 08h size: 8 bits 7.1.19 max_lat?maximum latency register (lan controller?b1:d8:f0) offset address: 3fh attribute: ro default value: 38h size: 8 bits bit description 7:0 interrupt line (int_ln) ?r/w. identifies the system interrupt line to which the lan controller?s pci interrupt request pin (as defined in the interrupt pin register) is routed. bit description 7:0 interrupt pin (int_pn) ?ro. hardwired to 01h to indicate that the lan controller?s interrupt request is connected to pirqa#. however, in the ich2 implementation, when the lan controller interrupt is generated pirq[e]# will go active, not pirq[a]#. bit description 7:0 minimum grant (min_gnt)?ro. indicates the amount of time (in increments of 0.25 s) that the lan controller needs to retain ownership of the pci bus when it initiates a transaction. bit description 7:0 maximum latency (max_lat)?ro. defines how often (in increments of 0.25 s) the lan controller needs to access the pci bus. lan controller registers (b1:d8:f0) 7-8 82801BA ich2 and 82801BAm ich2-m datasheet 7.1.20 cap_id?capability id register (lan controller?b1:d8:f0) offset address: dch attribute: ro default value: 01h size: 8 bits 7.1.21 nxt_ptr?next item pointer (lan controller?b1:d8:f0) offset address: ddh attribute: ro default value: 00h size: 8 bits 7.1.22 pm_cap?power management capabilities (lan controller?b1:d8:f0) offset address: de?dfh attribute: ro default value: fe22h size: 16 bits bit description 7:0 capability id (cap_id) ? ro. hardwired to 01h to indicate that the ich2?s integrated lan controller supports pci power management. bit description 7:0 next item pointer (nxt_ptr) ? rw. hardwired to 00b to indicate that power management is the last item in the capabilities list. bit description 15:11 pme support. hardwired to 11111b. this 5-bit field indicates the power states in which the lan controller may assert pme#. the lan controller supports wake-up in all power states. 10 d2 support. hardwired to 1 to indicate that the lan controller supports the d2 power state. 9 d1 support. hardwired to 1 to indicate that the lan controller supports the d1 power state. 8:6 auxiliary current. hardwired to 000b to indicate that the lan controller implements the data registers. the auxiliary power consumption is the same as the current consumption reported in the d3 state in the data register. 5 device specific initialization (dsi). hardwired to 1 to indicate that special initialization of this function is required (beyond the standard pci configuration header) before the generic class device driver is able to use it. dsi is required for the lan controller after d3-to-d0 reset. 4 reserved 3 pme clock. hardwired to 0 to indicate that the lan controller does not require a clock to generate a power management event. 2:0 version. hardwired to 010b to indicate that the lan controller complies with of the pci power management specification, revision 1.1. 82801BA ich2 and 82801BAm ich2-m datasheet 7-9 lan controller registers (b1:d8:f0) 7.1.23 pmcsr?power management control/status register (lan controller?b1:d8:f0) offset address: e0?e1h attribute: ro, r/w, r/wc default value: 0000h size: 16 bits 7.1.24 data?data register (lan controller?b1:d8:f0) offset address: e3h attribute: ro default value: 00h size: 8 bits note: the data register is an 8-bit read only register that provides a mechanism for the ich2?s integrated lan controller to report state dependent maximum power consumption and heat dissipation. the value reported in this register depends on the value written to the data select field in the pmcsr register. the power measurements defined in this register have a dynamic range of 0 to 2.55 w with 0.01 w resolution, scaled according to the data scale field in the pmcsr. the structure of the data register is given in table 7-3 . bit description 15 pme status ?r/wc. 1 = set upon occurrence of a wake-up event, independent of the state of the pme enable bit. 0 = software clears this bit by writing a 1 to the bit location. this also deasserts the pme# signal and clears the pme status bit in the power management driver register. when the pme# signal is enabled, the pme# signal reflects the state of the pme status bit. 14:13 data scale? ro. this field indicates the data register scaling factor. it equals 10b for registers zero through eight and 00b for registers nine through fifteen, as selected by the "data select" field. 12:9 data select? r/w. this field is used to select which data is reported through the data register and data scale field. 8 pme enable ?r/w. this bit enables the ich2?s integrated lan controller to assert pme#. 1 = enable pme# assertion when pme status is set. 0 = the device will not assert pme#. 7:5 reserved. 4 dynamic data? ro. hardwired to 0 to indicate that the device does not support the ability to monitor the power consumption dynamically. 3:2 reserved. 1:0 power state? r/w. this 2-bit field is used to determine the current power state of the integrated lan controller, and to put it into a new power state. the definition of the field values is as follows: 00 = d0 01 = d1 10 = d2 11 = d3 bit description 7:0 data value . state dependent power consumption and heat dissipation data. lan controller registers (b1:d8:f0) 7-10 82801BA ich2 and 82801BAm ich2-m datasheet 7.2 lan control / status registers (csr) table 7-3. data register structure data select data scale data reported 0 2 d0 power consumption 1 2 d1 power consumption 2 2 d2 power consumption 3 2 d3 power consumption 4 2 d0 power dissipated 5 2 d1 power dissipated 6 2 d2 power dissipated 7 2 d3 power dissipated 8 2 common function power dissipated 9?15 0 reserved table 7-4. ich2 integrated lan controller csr space offset register name/function default type 01h?00h scb status word 0000h r/wc 03h?02h scb command word 0000h r/w 07h?04h scb general pointer 0000 0000h r/w 0bh?08h port 0000 0000h r/w (special) 0dh?0ch reserved ? ? 0eh eeprom control register 00 r/w 0fh reserved ? ? 13h?10h mdi control register 0000 0000h r/w (special) 17h?14h receive dma byte count 0000 0000h ro 18h early receive interrupt 00h r/w 1a?19h flow control register 0000h r/w 1bh pmdr 00h r/wc 1ch general control 00 r/w 1dh general status n/a ro 1eh?3ch reserved ? ? 82801BA ich2 and 82801BAm ich2-m datasheet 7-11 lan controller registers (b1:d8:f0) 7.2.1 system control block status word register offset address: 00?01h attribute: r/wc, ro default value: 0000h size: 16 bits the ich2?s integrated lan controller places the status of its command and receive units and interrupt indications in this register for the processor to read. bit description 15 command unit (cu) executed (cx) ?r/wc. 1 = interrupt signaled because the cu has completed executing a command with its interrupt bit set. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 14 frame received (fr) ?r/wc. 1 = interrupt signaled because the receive unit (ru) has finished receiving a frame 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 13 cu not active (cna) ?r/wc. 1 = the command unit left the active state or entered the idle state. there are 2 distinct states of the cu. when configured to generate cna interrupt, the interrupt will be activated when the cu leaves the active state and enters either the idle or the suspended state. when configured to generate ci interrupt, an interrupt will be generated only when the cu enters the idle state. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 12 receive not ready (rnr) ?r/wc. 1 = interrupt signaled because the receive unit left the ready state. this may be caused by an ru abort command, a no resources situation, or set suspend bit due to a filled receive frame descriptor. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 11 management data interrupt (mdi) ?r/wc. 1 = set when a management data interface read or write cycle has completed. the management data interrupt is enabled through the interrupt enable bit (bit 29 in the management data interface control register in the csr). 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 10 software interrupt (swi) ?r/wc. 1 = set when software generates an interrupt. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 9 early receive (er) ?r/wc. 1 = indicates the occurrence of an early receive interrupt. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 8 flow control pause (fcp) ?r/wc. 1 = indicates flow control pause interrupt. 0 = software acknowledges the interrupt and clears this bit by writing a 1 to the bit position. 7:6 command unit status (cus) ?ro. 00 = idle 01 = suspended 10 = lpq (low priority queue) active 11 = hpq (high priority queue) active 5:2 receive unit status (rus) ?ro. 0000 = idle 1000 = reserved 0001 = suspended 1001 = suspended with no more rbds 0010 = no resources 1010 = no resources due to no more rbds 0011 = reserved 1011 = reserved 0100 = ready 1100 = ready with no rbds present 0101 = reserved 1101 = reserved 0110 = reserved 1110 = reserved 0111 = reserved 1111 = reserved 1:0 reserved. lan controller registers (b1:d8:f0) 7-12 82801BA ich2 and 82801BAm ich2-m datasheet 7.2.2 system control block command word register offset address: 02?03h attribute: r/w default value: 0000h size: 16 bits the processor places commands for the command and receive units in this register. interrupts are also acknowledged in this register. bit description 15 cx mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of a cx interrupt. 14 fr mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of an fr interrupt. 13 cna mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of a cna interrupt. 12 rnr mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of an rnr interrupt. 11 er mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of an er interrupt. 10 fcp mask ?r/w. 0 = interrupt not masked. 1 = disable the generation of an fcp interrupt. 9 software generated interrupt (si) ?wo. 0 = no effect. 1 = setting this bit causes the lan controller to generate an interrupt. 8 interrupt mask (im) ?r/w. this bit enables or disables the lan controller?s assertion of the inta# signal. this bit has higher precedence that the specific interrupt mask bits and the si bit. 0 = enable the assertion of inta#. 1 = disable the assertion of inta#. 82801BA ich2 and 82801BAm ich2-m datasheet 7-13 lan controller registers (b1:d8:f0) 7:4 command unit command (cuc). valid values are listed below. all other values are reserved. 0000 = nop: does not affect the current state of the unit. 0001 = cu start : start execution of the first command on the cbl. a pointer to the first cb of the cbl should be placed in the scb general pointer before issuing this command. the cu start command should only be issued when the cu is in the idle or suspended states (never when the cu is in the active state), and all of the previously issued command blocks have been processed and completed by the cu. sometimes it is only possible to determine that all command blocks are completed by checking that the complete bit is set in all previously issued command blocks. 0010 = cu resume: resume operation of the command unit by executing the next command. this command will be ignored if the cu is idle. 0011 = cu hpq start: start execution of the first command on the high priority cbl. a pointer to the first cb of the hpq cbl should be placed in the scb general pointer before issuing this command. 0100 = load dump counters address: tells the device where to write dump data when using the dump statistical counters or dump and reset statistical counters commands. this command must be executed at least once before any usage of the dump statistical counters or dump and reset statistical counters commands. the address of the dump area must be placed in the general pointer register. 0101 = dump statistical counters: tells the device to dump its statistical counters to the area designated by the load dump counters address command. 0110 = load cu base: the device?s internal cu base register is loaded with the value in the csb general pointer. 0111 = dump and reset statistical counters: tells the device to dump its statistical counters to the area designated by the load dump counters address command, and then to clear these counters. 1010 = cu static resume: resume operation of the command unit by executing the next command. this command will be ignored if the cu is idle. this command should be used only when the cu is in the suspended state and has no pending cu resume commands. 1011 = cu hpq resume: resume execution of the first command on the hpq cbl. this command will be ignored if the hpq was never started. 3 reserved. 2:0 receive unit command (ruc). valid values are: 000 = nop: does not affect the current state of the unit. 001 = ru start: enables the receive unit. the pointer to the rfa must be placed in the scb general pointer before using this command. the device pre-fetches the first rfd and the first rbd (if in flexible mode) in preparation to receive incoming frames that pass its address filtering. 010 = ru resume: resume frame reception (only when in suspended state). 011 = rcv dma redirect: resume the rcv dma when configured to "direct dma mode." the buffers are indicated by an rbd chain which is pointed to by an offset stored in the general pointer register (this offset will be added to the ru base). 100 = ru abort: abort ru receive operation immediately. 101 = load header data size (hds): this value defines the size of the header portion of the rfds or receive buffers. the hds value is defined by the lower 14 bits of the scb general pointer, so bits 31:15 should always be set to zeros when using this command. once a load hds command is issued, the device expects only to find header rfds, or be used in "rcv direct dma mode" until it is reset. note that the value of hds should be an even, non-zero number. 110 = load ru base: the device?s internal ru base register is loaded with the value in the scb general pointer. 111 = rbd resume: resume frame reception into the rfa. this command should only be used when the ru is already in the "no resources due to no rbds" state or the "suspended with no more rbds" state. bit description lan controller registers (b1:d8:f0) 7-14 82801BA ich2 and 82801BAm ich2-m datasheet 7.2.3 system control block general pointer register offset address: 04?07h attribute: r/w default value: 0000 0000h size: 32 bits 7.2.4 port register offset address: 08?0bh attribute: r/w (special) default value: 0000 0000h size: 32 bits the port interface allows the processor to reset the ich2?s internal lan controller or perform an internal self test. the port dword may be written as a 32-bit entity, two 16-bit entities, or four 8-bit entities. the lan controller will only accept the command after the high byte (offset 0bh) is written; therefore, the high byte must be written last. bit description 15:0 scb general pointer. the scb general pointer register is programmed by software to point to various data structures in main memory depending on the current scb command word. bit description 31:4 pointer field. a 16-byte aligned address must be written to this field when issuing a self-test command to the port interface.the results of the self test will be written to the address specified by this field. 3:0 port function selection. valid values are listed below. all other values are reserved. 0000 = port software reset: completely resets the lan controller (all csr and pci registers). this command should not be used when the device is active. if a port software reset is desired, software should do a selective reset (described below), wait for the port register to be cleared (completion of the selective reset) and then issue the port software reset command. software should wait approximately 10 s after issuing this command before attempting to access the lan controller?s registers again. 0001 = self test: the self-test begins by issuing an internal selective reset followed by a general internal self-test of the lan controller. the results of the self-test are written to memory at the address specified in the pointer field of this register. the format of the self- test result is shown in table 7-5 . after completing the self-test and writing the results to memory, the lan controller will execute a full internal reset and will re-initialize to the default configuration. self-test does not generate an interrupt of similar indicator to the host processor upon completion. 0010 = selective reset: sets the cu and ru to the idle state, but otherwise maintains the current configuration parameters (ru and cu base, hdssize, error counters, configure information and individual/multicast addresses are preserved). software should wait approximately 10 s after issuing this command before attempting to access the lan controller?s registers again. 82801BA ich2 and 82801BAm ich2-m datasheet 7-15 lan controller registers (b1:d8:f0) 7.2.5 eeprom control register offset address: 0eh attribute: ro, r/w default value: 00h size: 8 bits the eeprom control register is a 16-bit field that enables a read from and a write to the external eeprom. table 7-5. self-test results format bit description 31:13 reserved 12 general self-test result. 0 = pass 1 = fail 11:6 reserved 5 diagnose result. this bit provides the result of an internal diagnostic test of the serial subsystem. 0 = pass 1 = fail 4 reserved 3 register result. this bit provides the result of a test of the internal parallel subsystem registers. 0 = pass 1 = fail 2 rom content result. this bit provides the result of a test of the internal microcode rom. 0 = pass 1 = fail 1:0 reserved bit description 7:4 reserved 3 eeprom serial clock (eesk) ?r/w. toggling this bit clocks data into or out of the eeprom. software must ensure that this bit is toggled at a rate that meets the eeprom component?s minimum clock frequency specification. 0 = drives the ich2?s ee_shclk signal low. 1 = drives the ich2?s ee_shclk signal high. 2 eeprom chip select (eecs) ?r/w. 0 = drives the ich2?s ee_cs signal low, to disable the eeprom. this bit must be set to 0 for a minimum of 1 s between consecutive instruction cycles. 1 = drives the ich2?s ee_cs signal high, to enable the eeprom. 1 eeprom serial data in (eedi) ?wo. note that this bit represents "data in" from the perspective of the eeprom device. the value of this bit is written to the eeprom when performing write operations. 0 eeprom serial data out (eedo) ?ro. note that this bit represents "data out" from the perspective of the eeprom device. this bit contains the value read from the eeprom when performing read operations. lan controller registers (b1:d8:f0) 7-16 82801BA ich2 and 82801BAm ich2-m datasheet 7.2.6 management data interface (mdi) control register offset address: 10?13h attribute: r/w (special) default value: 0000 0000h size: 32 bits the management data interface (mdi) control register is a 32-bit field and is used to read and write bits from the lan connect component. this register may be written as a 32-bit entity, two 16-bit entities, or four 8-bit entities. the lan controller will only accept the command after the high byte (offset 13h) is written; therefore, the high byte must be written last. 7.2.7 receive dma byte count register offset address: 14?17h attribute: ro default value: 0000 0000h size: 32 bits bit description 31:30 these bits are reserved and should be set to 00b. 29 interrupt enable. 1 = enables the lan controller to assert an interrupt to indicate the end of an mdi cycle. 0 = disable. 28 ready. 1 = set by the lan controller at the end of an mdi transaction. 0 = expected to be reset by software at the same time the command is written. 27:26 opcode. these bits define the opcode: 00 = reserved 01 = mdi write 10 = mdi read 11 = reserved 25:21 lan connect address. this field of bits contains the lan connect address. 20:16 lan connect register address. this field of bits contains the lan connect register address. 15:0 data. in a write command, software places the data bits in this field, and the lan controller transfers the data to the external lan connect component. during a read command, the lan controller reads these bits serially from the lan connect, and software reads the data from this location. bit description 31:0 receive dma byte count ?ro. keeps track of how many bytes of receive data have been passed into host memory via dma. 82801BA ich2 and 82801BAm ich2-m datasheet 7-17 lan controller registers (b1:d8:f0) 7.2.8 early receive interrupt register offset address: 18h attribute: r/w default value: 00h size: 8 bits the early receive interrupt register allows the internal lan controller to generate an early interrupt depending on the length of the frame. the lan controller will generate an interrupt at the end of the frame, regardless of whether or not early receive interrupts are enabled. note: it is recommended that software not utilize this register unless receive interrupt latency is a critical performance issue in that particular software environment. using this feature may reduce receive interrupt latency, but will also result in the generation of more interrupts, which can degrade system efficiency and performance in some environments. bit description 7:0 early receive count ?r/w. when some non-zero value x is programmed into this register, the lan controller sets the er bit in the scb status word register and assert inta# when the byte count indicates that there are x quadwords remaining to be received in the current frame (based on the type/length field of the received frame). no early receive interrupt will be generated if a value of 00h (the default value) is programmed into this register. lan controller registers (b1:d8:f0) 7-18 82801BA ich2 and 82801BAm ich2-m datasheet 7.2.9 flow control register offset address: 19?1ah attribute: ro, r/w (special) default value: 0000h size: 16 bits bit description 15:13 reserved 12 fc paused low ?ro. 1 = set when the lan controller receives a pause low command with a value greater than zero. 0 = cleared when the fc timer reaches zero, or a pause frame is received. 11 fc paused ?ro. 1 = set when the lan controller receives a pause command regardless of its cause (fifo reaching flow control threshold, fetching a receive frame descriptor with its flow control pause bit set, or software writing a 1 to the xoff bit). 0 = cleared when the fc timer reaches zero. 10 fc full ?ro. 1 = set when the lan controller sends a pause command with a value greater than zero. 0 = cleared when the fc timer reaches zero. 9 xoff ?r/w (special). this bit should only be used if the lan controller is configured to operate with ieee frame-based flow control. 1 = writing a 1 to this bit forces the xoff request to 1 and causes the lan controller to behave as if the fifo extender is full. this bit will also be set to 1 when an xoff request due to an "rfd xoff" bit. 0 = this bit can only be cleared by writing a 1 to the xon bit (bit 8 in this register). 8 xon ?wo. this bit should only be used if the lan controller is configured to operate with ieee frame-based flow control. 1 = writing a 1 to this bit resets the xoff request to the lan controller, clearing bit 9 in this register. 0 = this bit always returns 0 on reads. 7:3 reserved 2:0 flow control threshold ?r/w. the lan controller can generate a flow control pause frame when its receive fifo is almost full. the value programmed into this field determines the number of bytes still available in the receive fifo when the pause frame is generated. free bytes bits 2:0 in receive fifo comment 000 0.50 kb fast system (recommended default) 001 1.00 kb 010 1.25 kb 011 1.50 kb 100 1.75 kb 101 2.00 kb 110 2.25 kb 111 2.50 kb slow system 82801BA ich2 and 82801BAm ich2-m datasheet 7-19 lan controller registers (b1:d8:f0) 7.2.10 power management driver (pmdr) register offset address: 1bh attribute: r/wc default value: 00h size: 8 bits the ich2?s internal lan controller provides an indication in the pmdr that a wake-up event has occurred. 7.2.11 general control register offset address: 1ch attribute: r/w default value: 00h size: 8 bits bit description 7 link status change indication? r/wc. 1 = the link status change bit is set following a change in link status. 0 = software clears this bit by writing a 1 to the bit location. 6 magic packet? r/wc. 1 = this bit is set when a magic packet is received regardless of the magic packet wake-up disable bit in the configuration command and the pme enable bit in the power management control/ status register. 0 = software clears this bit by writing a 1 to the bit location. 5 interesting packet? r/wc. 1 = this bit is set when an ?interesting? packet is received. interesting packets are defined by the lan controller packet filters. 0 = software clears this bit by writing a 1 to the bit location. 4:1 reserved. 0 pme status? r/wc. this bit is a reflection of the pme status bit in the power management control/status register (pmcsr). 1 = set upon a wake-up event, independent of the pme enable bit. 0 = software clears this bit by writing a 1 to the bit location. this also clears the pme status bit in the pmcsr and deasserts the pme signal. bit description 7:4 reserved. these bits should be set to 0000b. 3 lan connect software reset? r/w. 1 = software can set this bit to force a reset condition on the lan connect interface. 0 = cleared by software to begin normal lan connect operating mode. software must not attempt to access the lan connect interface for at least 1 ms after clearing this bit. 2 reserved. this bit should be set to 0. 1 deep power-down on link down enable. 1 = enable. the ich2?s internal lan controller may enter a deep power-down state (sub 3 ma) in the d2 and d3 power states while the link is down. in this state, the lan controller does not keep link integrity. this state is not supported for point-to-point connection of two end stations. 0 = disable 0 reserved. lan controller registers (b1:d8:f0) 7-20 82801BA ich2 and 82801BAm ich2-m datasheet 7.2.12 general status register offset address: 1dh attribute: ro default value: n/a size: 8 bits 7.2.13 statistical counters the ich2?s integrated lan controller provides information for network management statistics by providing on-chip statistical counters that count a variety of events associated with both transmit and receive. the counters are updated by the lan controller when it completes the processing of a frame (i.e., when it has completed transmitting a frame on the link or when it has completed receiving a frame). the statistical counters are reported to the software on demand by issuing the dump statistical counters command or dump and reset statistical counters command in the scb command unit command (cuc) field. bit description 7:3 reserved. 2 duplex mode. this bit indicates the wire duplex mode. 1 = full duplex 0 = half duplex 1 speed. this bit indicates the wire speed: 1 = 100 mbps 0 = 10 mbps 0 link status indication. this bit indicates the status of the link: 1 = valid 0 = invalid table 7-6. statistical counters id counter description 0 transmit good frames this counter contains the number of frames that were transmitted properly on the link. it is updated only after the actual transmission on the link is completed, not when the frame was read from memory as is done for the transmit command block status. 4 transmit maximum collisions (maxcol) errors this counter contains the number of frames that were not transmitted because they encountered the configured maximum number of collisions. 8 transmit late collisions (latecol) errors this counter contains the number of frames that were not transmitted since they encountered a collision later than the configured slot time. 12 transmit underrun errors a transmit underrun occurs because the system bus cannot keep up with the transmission. this counter contains the number of frames that were either not transmitted or retransmitted due to a transmit dma underrun. if the lan controller is configured to retransmit on underrun, this counter may be updated multiple times for a single frame. 16 transmit lost carrier sense (crs) this counter contains the number of frames that were transmitted by the lan controller despite the fact that it detected the deassertion of crs during the transmission. 20 transmit deferred this counter contains the number of frames that were deferred before transmission due to activity on the link. 24 transmit single collisions this counter contains the number of transmitted frames that encountered one collision. 82801BA ich2 and 82801BAm ich2-m datasheet 7-21 lan controller registers (b1:d8:f0) 28 transmit multiple collisions this counter contains the number of transmitted frames that encountered more than one collision. 32 transmit total collisions this counter contains the total number of collisions that were encountered while attempting to transmit. this count includes late collisions and frames that encountered maxcol. 36 receive good frames this counter contains the number of frames that were received properly from the link. it is updated only after the actual reception from the link is completed and all the data bytes are stored in memory. 40 receive crc errors this counter contains the number of aligned frames discarded because of a crc error. this counter is updated, if needed, regardless of the receive unit state. the receive crc errors counter is mutually exclusive of the receive alignment errors and receive short frame errors counters. 44 receive alignment errors this counter contains the number of frames that are both misaligned (for example, crs deasserts on a non-octal boundary) and contain a crc error. the counter is updated, if needed, regardless of the receive unit state. the receive alignment errors counter is mutually exclusive of the receive crc errors and receive short frame errors counters. 48 receive resource errors this counter contains the number of good frames discarded due to unavailability of resources. frames intended for a host whose receive unit is in the no resources state fall into this category. if the lan controller is configured to save bad frames and the status of the received frame indicates that it is a bad frame, the receive resource errors counter is not updated. 52 receive overrun errors this counter contains the number of frames known to be lost because the local system bus was not available. if the traffic problem persists for more than one frame, the frames that follow the first are also lost; however, because there is no lost frame indicator, they are not counted. 56 receive collision detect (cdt) this counter contains the number of frames that encountered collisions during frame reception. 60 receive short frame errors this counter contains the number of received frames that are shorter than the minimum frame length. the receive short frame errors counter is mutually exclusive to the receive alignment errors and receive crc errors counters. a short frame will always increment only the receive short frame errors counter. 64 flow control transmit pause this counter contains the number of flow control frames transmitted by the lan controller. this count includes both the xoff frames transmitted and xon (pause(0)) frames transmitted. 68 flow control receive pause this counter contains the number of flow control frames received by the lan controller. this count includes both the xoff frames received and xon (pause(0)) frames received. 72 flow control receive unsupported this counter contains the number of mac control frames received by the lan controller that are not flow control pause frames. these frames are valid mac control frames that have the predefined mac control type value and a valid address but has an unsupported opcode. 76 receive tco frames this counter contains the number of tco packets received by the lan controller. 78 transmit tco frames this counter contains the number of tco packets transmitted. table 7-6. statistical counters id counter description lan controller registers (b1:d8:f0) 7-22 82801BA ich2 and 82801BAm ich2-m datasheet the statistical counters are initially set to zero by the ich2?s integrated lan controller after reset. they cannot be preset to anything other than zero. the lan controller increments the counters by internally reading them, incrementing them and writing them back. this process is invisible to the processor and pci bus. in addition, the counters adhere to the following rules: ? the counters are wrap-around counters. after reaching ffffffffh the counters wrap around to 0. ? the lan controller updates the required counters for each frame. it is possible for more than one counter to be updated as multiple errors can occur in a single frame. ? the counters are 32 bits wide and their behavior is fully compatible with the ieee 802.1 standard. the lan controller supports all mandatory and recommend statistics functions through the status of the receive header and directly through these statistical counters. the processor can access the counters by issuing a dump statistical counters scb command. this provides a ?snapshot?, in main memory, of the internal lan controller statistical counters. the lan controller supports 21 counters. the dump could consist of the either 16, 19, or all 21 counters, depending on the status of the extended statistics counters and tco statistics configuration bits in the configuration command. 82801BA ich2 and 82801BAm ich2-m datasheet 8-1 hub interface to pci bridge registers (d30:f0) hub interface to pci bridge registers (d30:f0) 8 the hub interface to pci bridge resides in pci device 30, function 0 on bus #0. this portion of the ich2 implements the buffering and control logic between pci and the hub interface. the arbitration for the pci bus is handled by this pci device. the pci decoder in this device must decode the ranges for the hub interface. all register contents will be lost when core well power is removed. 8.1 pci configuration registers (d30:f0) note: registers that are not shown should be treated as reserved (see section 6.2 for details). . table 8-1. pci configuration map (hub-pci?d30:f0) offset mnemonic register name/function default type 00?01h vid vendor id 8086h ro 02?03h did device id 244eh (ich2) 2448h (ich2-m) ro 04?05h cmd pci device command register 0001h r/w 06?07h pd_sts pci device status register 0080h r/w 08h revid revision id see note ro 0ah scc sub class code 04h ro 0bh bcc base class code 06h ro 0dh pmlt primary master latency timer 00h ro 0eh headtyp header type 01h ro 18h pbus_num primary bus number 00h ro 19h sbus_num secondary bus number 00h r/w 1ah sub_bus_num subordinate bus number 00h r/w 1bh smlt secondary master latency timer 00h r/w 1ch iobase io base register f0h r/w 1dh iolim io limit register 00h r/w 1e?1fh secsts secondary status register 0280h r/w 20?21h membase memory base fff0h r/w 22?23h memlim memory limit 0000h r/w 24?25h pref_mem_bas e prefetchable memory base 0000h ro 26?27h pref_mem_mlt prefetchable memory limit 0000h ro 30?31h iobase_hi i/o base upper 16 bits 0000h ro 32?33h iolimit_hi i/o limit upper 16 bits 0000h ro hub interface to pci bridge registers (d30:f0) 8-2 82801BA ich2 and 82801BAm ich2-m datasheet note: refer to the specification update for the value of the revision id register 8.1.1 vid?vendor id register (hub-pci?d30:f0) offset address: 00?01h attribute: ro default value: 8086h size: 16 bits 8.1.2 did?device id register (hub-pci?d30:f0) offset address: 02?03h attribute: ro size: 16 bits 3ch int_line interrupt line 00h ro 3e?3fh bridge_cnt bridge control 0000h r/w 40h bridge_cnt2 bridge control 2 00 r/w 50?51h cnf ich2 configuration register 0000h r/w 70h mtt multi-transaction timer 20h r/w 82h pci_mast_sts pci master status 00h r/w 90h err_cmd error command register 00h r/w 92h err_sts error status register 00h r/w table 8-1. pci configuration map (hub-pci?d30:f0) (continued) offset mnemonic register name/function default type bit description 15:0 vendor identification number? ro. this is a 16-bit value assigned to intel. intel vid = 8086h. default value: 244eh (82801BA ich2) 2448h (82801BAm ich2-m) bit description 15:0 device identification number? ro. this is a 16 bit value assigned to the ich2 hub interface to pci bridge (i.e., device #2). 82801BA ich2 and 82801BAm ich2-m datasheet 8-3 hub interface to pci bridge registers (d30:f0) 8.1.3 cmd?command register (hub-pci?d30:f0) offset address: 04?05h attribute: r/w default value: 0001h size: 16 bits bit description 15:10 reserved. 9 fast back to back enable (fbe)?ro. hardwired to 0. the ich2 does not support this capability. 8 serr# enable (serr_en)? r/w. 1 = enable the ich2 to generate an nmi (or smi# if nmi routed to smi#) when the d30:f0 sse bit (offset 06h, bit 14) is set. 0 = disable. 7 wait cycle control?ro. hardwired to 0 6 .parity error response? r/w. 1 = the ich2 is allowed to report parity errors detected on the hub interface. 0 = the ich2 will ignore parity errors on the hub interface. 5 vga palette snoop?ro. hardwired to 0. 4 postable memory write enable (pmwe)?ro. hardwired to 0. 3 special cycle enable (sce)?ro. hardwired to 0 by p2p bridge specification. 2 bus master enable (bme)? r/w. 1 = allows the hub interface-to-pci bridge to accept cycles from pci to run on the hub interface. note: this bit does not affect the cf8h and cfch i/o accesses. 0 = disable 1 memory space enable (mse)? r/w. the ich2 provides this bit as read/writable for software only. however, the ich2 ignores the programming of this bit, and runs hub interface memory cycles to pci. 0 i/o space enable (ioe)? r/w. the ich2 provides this bit as read/writable for software only. however, the ich2 ignores the programming of this bit and runs hub interface i/o cycles to pci that are not intended for usb, ide, or ac?97. hub interface to pci bridge registers (d30:f0) 8-4 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.4 pd_sts?primary device status register (hub-pci?d30:f0) offset address: 06?07h attribute: r/wc default value: 0080h size: 16 bits for the writable bits in this register, writing a 1 will clear the bit. writing a 0 to the bit will have no effect. 8.1.5 revid?revision id register (hub-pci?d30:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits bit description 15 detected parity error (dpe)? r/wc. 1 = indicates that the ich2 detected a parity error on the hub interface. this bit gets set even if the parity error response bit (offset 04, bit 6) is not set. 0 = software clears this bit by writing a 1 to the bit location. 14 received system error (sse)? r/wc. 1 = an address, or command parity error, or special cycles data parity error has been detected on the pci bus, and the parity error response bit (d30:f0, offset 04h, bit 6) is set. if this bit is set because of parity error and the d30:f0 serr_en bit (offset 04h, bit 8) is also set, the ich2 will generate an nmi (or smi# if nmi routed to smi#) 0 = software clears this bit by writing a 1 to the bit location. 13 received master abort (rma) ?r/wc. 1 = ich2 received a master abort from the hub interface device. 0 = software clears this bit by writing a 1 to the bit location. 12 received target abort (rta)? r/wc. 1 = ich2 received a target abort from the hub interface device. the tco logic can cause an smi#, nmi, or interrupt based on this bit getting set. 0 = software clears this bit by writing a 1 to the bit location. 11 signaled target abort (sta) ?r/wc. 1 = ich2 signals a target abort condition on the hub interface. 0 = software clears this bit by writing a 1 to the bit location. 10:9 devsel# timing status?ro. 00h = fast timing. this register applies to the hub interface; therefore, this field does not matter. 8 data parity error detected (dpd)? r/wc. since this register applies to the hub interface, the ich2 must interpret this bit differently than it is in the pci specification. 1 = ich2 detects a parity error on the hub interface and the parity error response bit in the command register (offset 04h, bit 6) is set. 0 = software clears this bit by writing a 1 to the bit location. 7 fast back to back?ro. hardwired to 1. 6 user definable features (udf)?ro. hardwired to 0. 5 66 mhz capable?ro. hardwired to 0. 4:0 reserved. bit description 7:0 revision identification number ?ro. 8-bit value that indicates the revision number for the ich2 hub interface to pci bridge. refer to the specification update for the value of the revision id register. 82801BA ich2 and 82801BAm ich2-m datasheet 8-5 hub interface to pci bridge registers (d30:f0) 8.1.6 scc?sub-class code register (hub-pci?d30:f0) offset address: 0ah attribute: ro default value: 04h size: 8 bits 8.1.7 bcc?base-class code register (hub-pci?d30:f0) offset address: 0bh attribute: ro default value: 06h size: 8 bits 8.1.8 pmlt?primary master latency timer register (hub-pci?d30:f0) offset address: 0dh attribute: ro default value: 00h size: 8 bits this register does not apply to hub interface. 8.1.9 headtyp?header type register (hub-pci?d30:f0) offset address: 0eh attribute: ro default value: 01h size: 8 bits bit description 7:0 sub-class code ?ro. this 8-bit value indicates the category of bridge for the ich2 hub interface to pci bridge. the code is 04h indicating a pci-to-pci bridge. bit description 7:0 base class code ?ro. this 8-bit value indicates the type of device for the ich2 hub interface to pci bridge. the code is 06h indicating a bridge device. bit description 7:3 master latency count. not implemented. 2:0 reserved. bit description 7 multi-function device?ro. this bit is 0 to indicate a single function device. 6:0 header type?ro. 8-bit field identifies the header layout of the configuration space, which is a pci- to-pci bridge in this case. hub interface to pci bridge registers (d30:f0) 8-6 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.10 pbus_num?primary bus number register (hub-pci?d30:f0) offset address: 18h attribute: ro default value: 00h size: 8 bits 8.1.11 sbus_num?secondary bus number register (hub-pci?d30:f0) offset address: 19h attribute: r/w default value: 00h size: 8 bits 8.1.12 sub_bus_num?subordinate bus number register (hub-pci?d30:f0) offset address: 1a attribute: r/w default value: 00h size: 8 bits 8.1.13 smlt?secondary master latency timer register (hub-pci?d30:f0) offset address: 1bh attribute: r/w default value: 00h size: 8 bits this master latency timer (mlt) controls the amount of time that the ich2 continues to burst data as a master on the pci bus. when the ich2 starts the cycle after being granted the bus, the counter is loaded and starts counting down from the assertion of frame#. if the internal grant to this device is removed, then the expiration of the mlt counter results in the deassertion of frame#. if the internal grant has not been removed, the ich2 can continue to own the bus. bit description 7:0 primary bus number ?ro. this field indicates the bus number of the hub interface and is hardwired to 00h. bit description 7:0 secondary bus number ?r/w. this field indicates the bus number of pci. note that when this number is equal to the primary bus number (i.e., bus #0), the ich2 will run hub interface configuration cycles to this bus number as type 1 configuration cycles on pci. bit description 7:0 subordinate bus number ?r/w. this field specifies the highest pci bus number below the hub interface to pci bridge. if a type 1 configuration cycle from the hub interface does not fall in the secondary-to-subordinate bus ranges of device 30, the ich2 indicates a master abort back to the hub interface. bit description 7:3 master latency count ?r/w. this 5-bit value indicates the number of pci clocks, in 8-clock increments, that the ich2 remains as master of the bus. 2:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 8-7 hub interface to pci bridge registers (d30:f0) 8.1.14 iobase?i/o base register (hub-pci?d30:f0) offset address: 1ch attribute: r/w default value: f0h size: 8 bits 8.1.15 iolim?i/o limit register (hub-pci?d30:f0) offset address: 1dh attribute: r/w default value: 00h size: 8 bits bit description 7:4 i/o address base bits [15:12]? r/w. i/o base bits corresponding to address lines 15:12 for 4 kb alignment. bits 11:0 are assumed to be padded to 000h. 3:0 i/o addressing capability? ro. this is hardwired to 0h, indicating that the hub interface to pci bridge does not support 32-bit i/o addressing. this means that the i/o base register and i/o limit upper address registers must be read only. bit description 7:4 i/o address limit bits [15:12]? r/w. i/o base bits corresponding to address lines 15:12 for 4 kb alignment. bits 11:0 are assumed to be padded to fffh. 3:0 i/o addressing capability? ro. this is hardwired to 0h, indicating that the hub interface-to-pci bridge does not support 32-bit i/o addressing. this means that the i/o base register and i/o limit upper address registers must be read only. hub interface to pci bridge registers (d30:f0) 8-8 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.16 secsts?secondary status register (hub-pci?d30:f0) offset address: 1e?1fh attribute: r/w default value: 0280h size: 16 bits for the writable bits in this register, writing a 1 will clear the bit. writing a 0 to the bit will have no effect. bit description 15 detected parity error (dpe) ?r/wc. 1 = ich2 detected a parity error on the pci bus. 0 = software clears this bit by writing a 1 to the bit position. 14 received system error (sse)? r/wc. 1 = serr# assertion is received on pci. 0 = software clears this bit by writing a 1 to the bit position. 13 received master abort (rma) ?r/wc. 1 = hub interface to pci cycle is master-aborted on pci. 0 = software clears this bit by writing a 1 to the bit position. 12 received target abort (rta) ?r/wc. 1 = hub interface to pci cycle is target-aborted on pci. for ?completion required? cycles from the hub interface, this event should also set the signaled target abort in the primary status register in this device and the ich2 must send the ?target abort? status back to the hub interface. 0 = software clears this bit by writing a 1 to the bit position. 11 signaled target abort (sta)?ro. the ich2 does not generate target aborts. 10:9 devsel# timing status?ro. 01h = medium timing. 8 data parity error detected (dpd) ?r/wc. 1 = the ich2 sets this bit when all of the following three conditions are met: - the parity error response enable bit in the bridge control register (bit 0, offset 3eh) is set - usb, ac?97 or ide is a master - perr# asserts during a write cycle or a parity error is detected internally during a read cycle 0 = software clears this bit by writing a 1 to the bit position. 7 fast back to back?ro. hardwired to 1 to indicate that the pci to hub interface target logic is capable of receiving fast back-to-back cycles. 6 user definable features (udf)?ro. hardwired to 0. 5 66 mhz capable?ro. hardwired to 0. 4:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 8-9 hub interface to pci bridge registers (d30:f0) 8.1.17 membase?memory base register (hub-pci?d30:f0) offset address: 20?21h attribute: r/w default value: fff0h size: 16 bits this register defines the base of the hub interface to pci non-prefetchable memory range. since the ich2 forwards all hub interface memory accesses to pci, the ich2 only uses this information for determining when not to accept cycles as a target. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be 0. thus, the bottom of the defined memory address range will be aligned to a 1 mb boundary. 8.1.18 memlim?memory limit register (hub-pci?d30:f0) offset address: 22?23h attribute: r/w default value: 0000h size: 16 bits this register defines the upper limit of the hub interface to pci non-prefetchable memory range. since the ich2 will forward all hub interface memory accesses to pci, the ich2 will only use this information for determining when not to accept cycles as a target. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be fffffh. thus, the top of the defined memory address range will be aligned to a 1 mb boundary. 8.1.19 pref_mem_base?prefetchable memory base register (hub-pci?d30:f0) offset address: 24h?25h attribute: r/w default value: 0000fff0h size: 16-bit bit description 15:4 memory address base ?r/w. defines the base of the memory range for pci. these 12 bits correspond to address bits 31:20. 3:0 reserved. bit description 15:4 memory address limit ?r/w. defines the top of the memory range for pci. these 12 bits correspond to address bits 31:20. 3:0 reserved. bit description 15:4 prefetchable memory address base? r/w. defines the base address of the prefetchable memory address range for pci. these 12 bits correspond to address bits 31:20. 3:0 reserved. ro. hub interface to pci bridge registers (d30:f0) 8-10 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.20 pref_mem_mlt?prefetchable memory limit register (hub-pci?d30:f0) offset address: 26h?27h attribute: r/w default value: 00000000h size: 16-bit 8.1.21 iobase_hi?i/o base upper 16 bits register (hub-pci?d30:f0) offset address: 30?31h attribute: ro default value: 0000h size: 16 bits 8.1.22 iolim_hi?i/o limit upper 16 bits register (hub-pci?d30:f0) offset address: 32?33h attribute: ro default value: 0000h size: 16 bits 8.1.23 int_line?interrupt line register (hub-pci?d30:f0) offset address: 3ch attribute: ro default value: 00h size: 8 bits bit description 15:4 prefetchable memory address limit? rw. defines the limit address of the prefetchable memory address range for pci. these 12 bits correspond to address bits 31:20. 3:0 reserved. ro bit description 15:0 i/o address base upper 16 bits [31:16]?ro. not supported; hardwired to 0. bit description 15:0 i/o address limit upper 16 bits [31:16]?ro. not supported; hardwired to 0. bit description 7:0 interrupt line routing?ro. hardwired to 00h. the bridge does not generate interrupts, and interrupts from downstream devices are routed around the bridge. 82801BA ich2 and 82801BAm ich2-m datasheet 8-11 hub interface to pci bridge registers (d30:f0) 8.1.24 bridge_cnt?bridge control register (hub-pci?d30:f0) offset address: 3e?3fh attribute: r/w default value: 0000h size: 16 bits 8.1.25 bridge_cnt2?bridge control register 2 (hub-pci?d30:f0) offset address: 40h attribute: r/w default value: 00h size 8 bits bit description 15:8 reserved. 7 fast back to back enable?ro. hardwired to 0. the pci logic will not generate fast back-to-back cycles on the pci bus. 6 secondary bus reset?ro. hardwired to 0. the ich2 does not follow the p2p bridge reset scheme; software-controlled resets are implemented in the pci-lpc device. 5 master abort mode? r/w. the ich2 ignores this bit. however, this bit is read/write for software compatibility. the ich2 must handle master aborts as if this bit is reset to 0. 4 reserved. 3 vga enable ?r/w. 1 = enable. indicates that the vga device is on pci. therefore, the pci to hub interface decoder will not accept memory cycles in the range a0000h?bf fffh. note that the ich2 will never take i/o cycles in the vga range from pci. 0 = no vga device on pci. 2 isa enable? r/w. the ich2 ignores this bit. however, this bit is read/write for software compatibility. since the ich2 forwards all i/o cycles that are not in the usb, ac?97, or ide ranges to pci, this bit would have no effect. 1 serr# enable? r/w. 1 = enable. if this bit is set and bit 8 in cmd register (d30:f0 offset 04h) is also set, the ich2 sets the sse bit in pd_sts register (d30:f0, offset 06h, bit 14) and also generate an nmi (or smi# if nmi routed to smi) when the serr# signal is asserted. 0 = disable 0 parity error response enable? r/w. 1 = enable the hub interface to pci bridge for parity error detection and reporting on the pci bus. 0 = disable bit description 7:1 reserved 0 pci_dac_en? r/w. allows ich2 to recognize external pci masters performing dac on pci. 0 = disable. 1 = enable. hub interface to pci bridge registers (d30:f0) 8-12 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.26 cnf?ich2 configuration register (hub-pci?d30:f0) offset address: 50?51h attribute: r/w default value: 0000h size: 16 bits 8.1.27 mtt?multi-transaction timer register (hub-pci?d30:f0) offset address: 70h attribute: r/w default value: 20h size: 8 bits mtt is an 8-bit register that controls the amount of time that the ich2?s arbiter allows a pci initiator to perform multiple back-to-back transactions on the pci bus. the ich2?s mtt mechanism is used to guarantee a fair share of the primary pci bandwidth to an initiator that performs multiple back-to-back transactions to fragmented memory ranges (and as a consequence it can not use long burst transfers). the number of clocks programmed in the mtt represents the guaranteed time slice (measured in pci clocks) allotted to the current agent, after which the arbiter grants another agent that is requesting the bus. the mtt value must be programmed with 8 clock granularity in the same manner as mlt. for example, if the mtt is programmed to 18h, the selected value corresponds to the time period of 24 pci clocks.the default value of mtt is 20h (32 pci clocks). note: programming the mtt to a value of 00h disables this function, which could cause starvation issues for some pci master devices. programming of the mtt to anything less than 16 clocks will not allow the grant-to-frame# latency to be 16 clocks. the mtt timer will time-out before the grant-to-frame# trigger causing a re-arbitration. bit description 15:10 reserved. 9 hp_pci_en ?r/w. high priority pci enable. 1 = enables a mode where the req[0]#/gnt[0]# signal pair has a higher arbitration priority. 0 = all pci req#/gnt pairs have the same arbitration priority. 8 hole enable (15 mb?16 mb)? r/w. 1 = enables the 15 mb to 16 mb hole in the dram. 0 = disable 7:3 reserved. 2 discard timer mode. this bit shortens all of the delayed transaction discard timers to 128 pci clocks. it controls how long the ich2-m will wait before flushing previously requested prefetched read data due to a delayed transaction, and then servicing a different request. 0 = 1024 pci clocks (32 us) (default). 1 = 128 pci clocks (4 us). 1 32-clock retry enable? r/w. system bios must set this bit for pci compliance. 1 = when a pci device is running a locked memory read cycle, while all other bus masters are waiting to run locked cycles, concurrent with a lpc dma transfer, this bit, when set allows the ich2 to retry the locked memory read cycle. 0 = if this bit is not set, under the same circumstance, the bus will not be released since all other masters see the lock in use. 0 reserved. bit description 7:3 multi-transaction timer count value? r/w. this field specifies the amount of time that grant remains asserted to a master continuously asserting its request for multiple transfers. this field specifies the count in an 8-clock (pci clock) granularity. 2:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 8-13 hub interface to pci bridge registers (d30:f0) 8.1.28 pci_mast_sts?pci master status register (hub-pci?d30:f0) offset address: 82h attribute: r/wc default value: 00h size: 8 bits 8.1.29 err_cmd?error command register (hub-pci?d30:f0) offset address: 90h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core this register configures the ich2?s device 30 responses to various system errors. the actual assertion of the internal serr# (routed to cause nmi# or smi#) is enabled via the pci command register. bit description 7 internal pci master request status (int_mreq_sts)? r/wc. 1 = the ich2?s internal dma controller or lpc has requested use of the pci bus. 0 = software clears this bit by writing a 1 to the bit position. 6 internal lan master request status (lan_mreq_sts)? r/wc. 1 = the ich2?s internal lan controller has requested use of the pci bus. 0 = software clears this bit by writing a 1 to the bit position. 5:0 pci master request status (pci_mreq_sts)? r/wc. allows software to see if a particular bus master has requested use of the pci bus. for example, bit 0 will be set if ich2 has detected req[0]# asserted and bit 5 will be set if ich2 detected req[5]# asserted. 1 = the associated pci master has requested use of the pci bus. 0 = software clears these bits by writing a 1 to the bit position. bit description 7:3 reserved. 2 serr# enable on receiving target abort (serr_rta_en)? r/w. 1 = enable. when serr_en is set, the ich2 will report serr# when serr_rta is set. 0 = disable 1 serr# enable on delayed transaction time-out (serr_dtt_en)? r/w. 1 = enable. when serr_en is set, the ich2 will report serr# when serr_dtt is set. 0 = disable. 0 reserved. hub interface to pci bridge registers (d30:f0) 8-14 82801BA ich2 and 82801BAm ich2-m datasheet 8.1.30 err_sts?error status register (hub-pci?d30:f0) offset address: 92h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core this register records the cause of system errors in device 30. the actual assertion of serr# is enabled via the pci command register. bit description 7:3 reserved. 2 serr# due to received target abort (serr_rta)? r/w. 1 = the ich2 sets this bit when the ich2 receives a target abort. if serr_en, the ich2 will also generate an serr# when serr_rta is set. 0 = this bit is cleared by writing a 1. 1 serr# due to delayed transaction time-out (serr_dtt)? r/w. 1 = when a pci master does not return for the data within 1 ms of the cycle?s completion, the ich2 clears the delayed transaction, and sets this bit. if both serr_dtt_en and serr_en are set, then ich2 will also generate an serr# when serr_dtt is set. 0 = this bit is cleared by writing a 1. 0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 9-1 lpc interface bridge registers (d31:f0) lpc interface bridge registers (d31:f0) 9 the lpc bridge function of the ich2 resides in pci device 31:function 0. this function contains many other functional units (e.g., dma and interrupt controllers, timers, power management, system management., gpio, rtc, and lpc configuration registers). registers and functions associated with other functional units (power management, gpio, usb, ide, etc.) are described in their respective sections. 9.1 pci configuration registers (d31:f0) note: registers that are not shown should be treated as reserved (see section 6.2 for details). . table 9-1. pci configuration map (lpc i/f?d31:f0) offset mnemonic register name default type 00h?01h vid vendor id 8086h ro 02h?03h did device id 2440h (ich2) 244ch (ich2-m) ro 04h?05h pcicmd pci command register 000fh r/w 06h?07h pcists pci device status register 0280h r/w 08h rid revision id see note ro 09h pi programming interface 00h ro 0ah scc sub class code 01h ro 0bh bcc base class code 06h ro 0eh headt header type 80h ro 40h?43h pmbase acpi base address register 00000001h r/w 44h acpi_cntl acpi control 00h r/w 4eh?4fh bios_cntl bios control register 0000h r/w 54h tco_cntl tco control 00h r/w 58h?5bh gpio_base gpio base address register 00000001h r/w 5ch gpio_cntl gpio control register 00h r/w 60h?63h pirq[ n ]_rout pirq[a?d] routing control 80808080h r/w 64h sirq_cntl serial irq control register 10h r/w 68h?6bh pirq[ n ]_rout pirq[e?h] routing control 80808080h r/w 88h d31_err_cfg device 31 error configuration register 00h r/w 8ah d31_err_sts device 31 error status register 00h r/w 90h?91h pci_dma_c pci dma configuration registers 0000h r/w a0h?cfh power management registers see section 9.8.1 lpc interface bridge registers (d31:f0) 9-2 82801BA ich2 and 82801BAm ich2-m datasheet note: refer to the specification update for the value of the revision id register. 9.1.1 vid?vendor id register (lpc i/f?d31:f0) offset address: 00?01h attribute: ro default value: 8086h size: 16-bit lockable: no power well: core 9.1.2 did?device id register (lpc i/f?d31:f0) offset address: 02?03h attribute: ro lockable: no size: 16-bit power well: core d0h?d3h gen_cntl general control 00000000h r/w d4h?d7h gen_sts general status 00000f00h r/w d8h rtc_conf real time clock configuration 00h r/w e0h com_dec lpc i/f com port decode ranges 00h r/w e1h lpcfdd_dec lpc i/f fdd & lpt decode ranges 00h r/w e2h snd_dec lpc i/f sound decode ranges 00h r/w e3h fwh_dec_en1 fwh decode enable 1 ffh r/w e4h?e5h gen1_dec lpc i/f general 1 decode range 0000h r/w e6h?e7h lpc_en lpc i/f enables 00h r/w e8h?ebh fwh_sel1 fwh select 1 00112233h r/w ech?edh gen2_dec lpc i/f general 2 decode range 0000h r/w eeh?efh fwh_sel2 fwh select 2 5678h r/w f0h fwh_dec_en2 fwh decode enable 2 0fh r/w f2h func_dis function disable register 00h r/w table 9-1. pci configuration map (lpc i/f?d31:f0) (continued) offset mnemonic register name default type bit description 15:0 vendor id value. this is a 16 bit value assigned to intel. intel vid = 8086h default value: 2440h (82801BA ich2) 244ch (82801BAm ich2-m) bit description 15:0 device id value. this is a 16 bit value assigned to the ich2 lpc bridge. 82801BA ich2 and 82801BAm ich2-m datasheet 9-3 lpc interface bridge registers (d31:f0) 9.1.3 pcicmd?pci command register (lpc i/f?d31:f0) offset address: 04?05h attribute: r/w default value: 000fh size: 16-bit lockable: no power well: core bit description 15:10 reserved. 9 fast back to back enable (fbe)?ro. hardwired to 0. 8 serr# enable (serr_en) ?r/w. 1 = enable. allow serr# to be generated. 0 = disable. 7 wait cycle control (wcc)?ro. hardwired to 0. 6 parity error response (per)? r/w. 1 = the ich will take normal action when a parity error is detected. 0 = no action is taken when detecting a parity error. 5 vga palette snoop (vps)?ro. hardwired to 0 4 postable memory write enable (pmwe)?ro. hardwired to 0 3 special cycle enable (sce). hardwired to 1. 2 bus master enable (bme)?ro. hardwired to 1 to indicate that bus mastering can not be disabled for function 0 (dma/isa master). 1 memory space enable (mse)?ro. hardwired to 1 to indicate that memory space can not be disabled for function 0 (lpc i/f). 0 i/o space enable (ioe)?ro. hardwired to 1 to indicate that the i/o space cannot be disabled for function 0 (lpc i/f). lpc interface bridge registers (d31:f0) 9-4 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.4 pcists?pci device status (lpc i/f?d31:f0) offset address: 06?07h attribute: r/wc default value: 0280h size:16-bit lockable: no power well: core 9.1.5 revid?revision id register (lpc i/f?d31:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits bit description 15 detected parity error (dpe) ?r/w. 1 = perr# signal goes active. set even if the per bit is 0. 0 = this bit is cleared by software writing a 1 to the bit position. 14 signaled system error (sse) ?r/w. 1 = set by the ich2 if the serr_en bit is set and the ich2 generates an serr# on function 0. the err_sts register can be read to determine the cause of the serr#. the serr# can be routed to cause smi#, nmi, or interrupt. 0 = this bit is cleared by software writing a 1 to the bit position. 13 master abort status (rma) ?r/w. 1 = ich2 generated a master abort on pci due to lpc i/f master or dma cycles. 0 = this bit is cleared by software writing a 1 to the bit position. 12 received target abort (rta) ?r/w. 1 = ich2 received a target abort during lpc i/f master or dma cycles to pci. 0 = this bit is cleared by software writing a 1 to the bit position. 11 signaled target abort (sta) ?r/w. 1 = ich2 generated a target abort condition on pci cycles claimed by the ich2 for ich2 internal registers or for going to lpc i/f. 0 = this bit is cleared by software writing a 1 to the bit position. 10:9 devsel# timing status (dev_sts) ?ro. 01 = medium timing. 8 data parity error detected (dped) ?r/wc. 1 = set when all three of the following conditions are true: - the ich2 is the initiator of the cycle, - the ich2 asserted perr# (for reads) or observed perr# (for writes), and - the per bit is set. 0 = this bit is cleared by software writing a 1 to the bit position. 7 fast back to back (fb2b)?ro. always 1. indicates ich2 as a target can accept fast back-to-back transactions. 6 user definable features (udf). hardwired to 0 5 66 mhz capable (66mhz_cap)?ro. hardwired to 0 4:0 reserved. bit description 7:0 revision identification number. 8-bit value that indicates the revision number for the lpc bridge. for the a-0 stepping, this value is 00h. refer to the specification update for the value of the revision id register 82801BA ich2 and 82801BAm ich2-m datasheet 9-5 lpc interface bridge registers (d31:f0) 9.1.6 pi?programming interface (lpc i/f?d31:f0) offset address: 09h attribute: ro default value: 00h size: 8 bits 9.1.7 scc?sub-class code register (lpc i/f?d31:f0) offset address: 0ah attribute: ro default value: 01h size: 8 bits 9.1.8 bcc?base-class code register (lpc i/f?d31:f0) offset address: 0bh attribute: ro default value: 06h size: 8 bits 9.1.9 headtyp?header type register (lpc i/f?d31:f0) offset address: 0eh attribute: ro default value: 80h size: 8 bits bit description 7:0 programming interface value. bit description 7:0 sub-class code. this 8-bit value indicates the category of bridge for the lpc pci bridge. bit description 7:0 base class code. this 8-bit value indicates the type of device for the lpc bridge. the code is 06h indicating a bridge device. bit description 7 multi-function device? ro. this bit is 1 to indicate a multi-function device. 6:0 header type? ro. this 8-bit field identifies the header layout of the configuration space. lpc interface bridge registers (d31:f0) 9-6 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.10 pmbase?acpi base address (lpc i/f?d31:f0) offset address: 40?43h attribute: r/w default value: 00000001h size: 32-bit lockable: no usage: acpi, legacy power well: core sets base address for acpi i/o registers, gpio registers and tco i/o registers. can be mapped anywhere in the 64 kb i/o space on 128-byte boundaries. 9.1.11 acpi_cntl?acpi control (lpc i/f?d31:f0) offset address: 44h attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: core bit description 31:16 reserved. 15:7 base address ?r/w. provides 128 bytes of i/o space for acpi, gpio, and tco logic. this is placed on a 128-byte boundary. 6:1 reserved. 0 resource indicator ?ro. tied to 1 to indicate i/o space. bit description 7:5 reserved. 4 acpi enable (acpi_en) ?r/w. 1 = decode of the i/o range pointed to by the acpi base register is enabled, and the acpi power management function is enabled. note that the apm power management ranges (b2/b3h) are always enabled and are not affected by this bit. 0 = disable. 3 reserved. 2:0 sci irq select (sci_irq_sel) ?r/w. specifies on which irq the sci will internally appear. if not using the apic, the sci must be routed to irq[9:11], and that interrupt is not sharable with the serirq stream, but is shareable with other pci interrupts. if using the apic, the sci can also be mapped to irq[20:23], and can be shared with other interrupts. 000 = irq9 001 = irq10 010 = irq11 011 = reserved 100 = irq20 (only available if apic enabled) 101 = irq21 (only available if apic enabled) 110 = rq22 (only available if apic enabled) 111 = irq23 (only available if apic enabled) 82801BA ich2 and 82801BAm ich2-m datasheet 9-7 lpc interface bridge registers (d31:f0) 9.1.12 bios_cntl (lpc i/f?d31:f0) offset address: 4e?4fh attribute: r/w default value: 0000h size: 16-bit lockable: no power well: core 9.1.13 tco_cntl?tco control (lpc i/f?d31:f0) offset address: 54h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core bit description 15:2 reserved. 1 bios lock enable (ble) ?r/w. 1 = enables setting the bioswe bit to cause smis. 0 = setting the bioswe will not cause smis. once set, this bit can only be cleared by a pcirst#. 0 bios write enable (bioswe) ?r/w. 1 = access to the bios space is enabled for both read and write cycles. when this bit is written from a 0 to a 1 and bios lock enable (ble) is also set, an smi# is generated. this ensures that only smm code can update bios. 0 = only read cycles result in fwh interface cycles. bit description 7:4 reserved. 3 tco interrupt enable (tco_int_en) ?r/w. this bit enables/disables the tco interrupt. 1 = enables tco interrupt, as selected by the tco_int_sel field. 0 = disables tco interrupt. 2:0 tco interrupt select (tco_int_sel) ?r/w. specifies which irq the tco internally appears. if not using the apic, the tco interrupt must be routed to irq[9:11], and that interrupt is not sharable with the serirq stream, but is shareable with other pci interrupts. if using the apic, the tco interrupt can also be mapped to irq[20:23], and can be shared with other interrupt. note that if the tcosci_en bit is set (bit 6 in the gpe0_en register), then the tco interrupt will be sent to the same interrupt as the sci, and the tco_int_sel bits will have no meaning. when the tco interrupt is mapped to apic interrupts 10 or 11, the signal is, in fact, active high. when the tco interrupt is mapped to irq[20, 21, or 22], the signal is active low and can be shared with pci interrupts that may be mapped to the same signals (irqs). 000 = irq9 001 = irq10 010 = irq11 011 = reserved 100 = irq20 (only available if apic enabled) 101 = irq21 (only available if apic enabled) 110 = irq22 (only available if apic enabled) 111 = irq23 (only available if apic enabled) lpc interface bridge registers (d31:f0) 9-8 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.14 gpiobase?gpio base address (lpc i/f?d31:f0) offset address: 58h?5bh attribute: r/w default value: 00000001h size: 32-bit lockable: no power well: core 9.1.15 gpio_cntl?gpio control (lpc i/f?d31:f0) offset address: 5ch attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 9.1.16 pirq[n]_rout?pirq[a,b,c,d] routing control (lpc i/f?d31:f0) offset address: pirqa?60h, pirqb?61h, attribute: r/w pirqc?62h, pirqd?63h default value: 80h size: 8-bit lockable: no power well: core bit description 31:16 reserved. 15:6 base address? r/w. provides the 64 bytes of i/o space for gpio. 5:1 reserved. 0 resource indicator ?ro. tied to 1 to indicate i/o space. bit description 7:5 reserved. 4 gpio enable (gpio_en) ?r/w. this bit enables/disables decode of the i/o range pointed to by the gpio base register and enables/disables the gpio function. 1 = enable 0 = disable 3:0 reserved. bit description 7 interrupt routing enable (irqen) ?r/w. note that bios must program this bit to 0 during post for any of the pirqs that are being used. the value of this bit may subsequently be changed by the os when setting up for i/o apic interrupt delivery mode. 0 = the corresponding pirq is routed to one of the isa-compatible interrupts specified in bits[3:0]. 1 = the pirq is not routed to the 8259. 6:4 reserved. 3:0 irq routing ?r/w. (isa compatible) 0000 = reserved 1000 = reserved 0001 = reserved 1001 = irq9 0010 = reserved 1010 = irq10 0011 = irq3 1011 = irq11 0100 = irq4 1100 = irq12 0101 = irq5 1101 = reserved 0110 = irq6 1110 = irq14 0111 = irq7 1111 = irq15 82801BA ich2 and 82801BAm ich2-m datasheet 9-9 lpc interface bridge registers (d31:f0) 9.1.17 serirq_cntl?serial irq control (lpc i/f?d31:f0) offset address: 64h attribute: r/w default value: 10h size: 8-bit lockable: no power well: core 9.1.18 pirq[n]_rout?pirq[e,f,g,h] routing control (lpc i/f?d31:f0) offset address: pirqe?68h, pirqf?69h, attribute: r/w pirqg?6ah, pirqh?6bh default value: 80h size: 8-bit lockable: no power well: core bit description 7 serial irq enable (sirqen) ?r/w. 1 = serial irqs will be recognized. the serirq pin will be configured as serirq. 0 = the buffer is input only and internally serirq will be a 1. 6 serial irq mode select (sirqmd) ?r/w. for systems using quiet mode, this bit should be set to 1 (continuous mode) for at least one frame after coming out of reset before switching back to quiet mode. failure to do so will result in the ich2 not recognizing serirq interrupts. 1 = the serial irq machine will be in continuous mode. 0 = the serial irq machine will be in quiet mode. 5:2 serial irq frame size (sirqsz) ?r/w. fixed field that indicates the size of the serirq frame. in the ich2, this field needs to be programmed to 21 frames (0100). this is an offset from a base of 17 which is the smallest data frame size. 1:0 start frame pulse width (sfpw) ?r/w. this is the number of pci clocks that the serirq pin will be driven low by the serial irq machine to signal a start frame. in continuous mode, the ich2 will drive the start frame for the number of clocks specified. in quiet mode, the ich2 will drive the start frame for the number of clocks specified minus one, as the first clock was driven by the peripheral. 00 = 4 clocks 01 = 6 clocks 10 = 8 clocks 11 = reserved bit description 7 interrupt routing enable (irqen) ?r/w. note that bios must program this bit to 0 during post for any of the pirqs that are being used. the value of this bit may subsequently be changed by the os when setting up for i/o apic interrupt delivery mode. 0 = the corresponding pirq is routed to one of the isa-compatible interrupts specified in bits[3:0]. 1 = the pirq is not routed to the 8259. 6:4 reserved. 3:0 irq routing ?r/w. (isa compatible) 0000 = reserved 1000 = reserved 0001 = reserved 1001 = irq9 0010 = reserved 1010 = irq10 0011 = irq3 1011 = irq11 0100 = irq4 1100 = irq12 0101 = irq5 1101 = reserved 0110 = irq6 1110 = irq14 0111 = irq7 1111 = irq15 lpc interface bridge registers (d31:f0) 9-10 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.19 d31_err_cfg?device 31 error configuration register (lpc i/f?d31:f0) offset address: 88h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core this register configures the ich2?s device 31 responses to various system errors. the actual assertion of serr# is enabled via the pci command register . 9.1.20 d31_err_sts?device 31 error status register (lpc i/f?d31:f0) offset address: 8ah attribute: r/wc default value: 00h size: 8-bit lockable: no power well: core this register configures the ich2?s device 31 responses to various system errors. the actual assertion of serr# is enabled via the pci command register. bit description 7:3 reserved. 2 serr# on received target abort enable (serr_rta_en) ?r/w. 1 = the ich2 will generate serr# when serr_rta is set if serr_en is set. 0 = disable. no serr# assertion on received target abort. 1 serr# on delayed transaction time-out enable (serr_dtt_en) ?r/w. 1 = the ich2 will generate serr# when serr_dtt bit is set if serr_en is set. 0 = disable. no serr# assertion on delayed transaction time-out. 0 reserved bit description 7:3 reserved. 2 serr# due to received target abort (serr_rta) ?r/wc. 1 = the ich2 sets this bit when it receives a target abort. if serr_en, the ich2 will also generate an serr# when serr_rta is set. 0 = software clears this bit by writing a 1 to the bit location. 1 serr# due to delayed transaction time-out (serr_dtt) ?r/wc. 1 = when a pci master does not return for the data within 1 ms of the cycle?s completion, the ich2 clears the delayed transaction and sets this bit. if both serr_dtt_en and serr_en are set, then ich2 will also generate an serr# when serr_dtt is set. 0 = software clears this bit by writing a 1 to the bit location. 0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 9-11 lpc interface bridge registers (d31:f0) 9.1.21 pci_dma_cfg?pci dma configuration (lpc i/f?d31:f0) offset address: 90h?91h attribute: r/w default value: 0000h size: 16-bit lockable: no power well: core 9.1.22 gen_cntl?general control register (lpc i/f?d31:f0) offset address: d0h?d3h attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: core bit description 15:14 channel 7 select ?r/w. 00 = reserved 01 = pc/pci dma 10 = reserved 11 = lpc i/f dma 13:12 channel 6 select ?r/w. same bit decode as for channel 7 11:10 channel 5 select ?r/w. same bit decode as for channel 7 9:8 reserved. 7:6 channel 3 select ?r/w. same bit decode as for channel 7 5:4 channel 2 select ?r/w. same bit decode as for channel 7 3:2 channel 1 select ?r/w. same bit decode as for channel 7 1:0 channel 0 select ?r/w. same bit decode as for channel 7 bit description 31:26 reserved. 25 req[5]#/gnt[5]# pc/pci protocol select (pcpcib_sel) ?r/w. 1 = when this bit is set to a 1, the pci req[5]#/gnt[5]# signal pair will use the pc/pci protocol as req[b]#/gnt[b]. the corresponding bits in the gpio_use_sel register must also be set to a 0. if the corresponding bits in the gpio_use_sel register are set to a 1, the signals will be used as a gpi and gpo. 0 = the req[5]#/gnt[5]# pins will function as a standard pci req/gnt signal pair. 24 hide isa bridge (hide_isa) ?r/w. 1 = software sets this bit to 1 to disable configuration cycle from being claimed by a pci-to-isa bridge. this prevents the operating system pci pnp from getting confused by seeing two isa bridges. it is required for the ich2 pci address line ad22 to connect to the pci-to-isa bridge?s idsel input. when this bit is 1, the ich2 does not assert ad22 during configuration cycles to the pci-to-isa bridge. 0 = the ich2 does not prevent ad22 from asserting during configuration cycles to the pci-to-isa bridge. 23:14 reserved. 13 coprocessor error enable (copr_err_en) ?r/w. 1 = when ferr# is low, ich2 generates irq13 internally and holds it until an i/o write to port f0h. it will also drive ignne# active. 0 = ferr# will not generate irq13 nor ignne#. 12 keyboard irq1 latch enable (irq1len) ?r/w. 1 = the active edge of irq1 will be latched and held until a port 60h read. 0 = irq1 will bypass the latch. lpc interface bridge registers (d31:f0) 9-12 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. rule 1: if bit 8 is 0, the ich2 does not decode any of the registers associated with the i/o apic or i/o (x) apic. the state of bit 7 is a ?don?t care? in this case. rule 2: if bit 8 is 1 and bit 7 is 0, the ich2 decodes the memory space associated with the i/o apic, but not the extra registers associated with the i/o (x) apic. rule 3: if bit 8 is 1 and bit 7 is 1, the ich2 decodes the memory space associated with both the i/o apic and the i/o (x) apic. this also enables pci masters to write directly to the register to cause interrupts (pci message interrupt). note that there is no separate way to disable pci message interrupts if the i/o (x) apic is enabled. this is not considered necessary. 11 mouse irq12 latch enable (irq12len) ?r/w. 1 = the active edge of irq12 will be latched and held until a port 60h read. 0 = irq12 will bypass the latch. 10:9 reserved 8 1 apic enable (apic_en) ?r/w. 1 = enables the internal i/o (x) apic and its address decode. 0 = disables internal i/o (x) apic. 7 1 enables i/o (x) extension enable (xapic_en) ?r/w. note that this bit is only valid if the aipc_en bit (bit 8) is also set to 1. 1 = enables the extra features (beyond standard i/o apic) associated with the i/o (x) apic. 0 = the i/o (x) apic extensions are not supported. 6 alternate access mode enable (altacc_en) ?r/w. 1 = alternate access mode enable 0 = alternate access mode disabled (default). alternate access mode allows reads to otherwise unreadable registers and writes otherwise unwriteable registers. 5:3 reserved. 2 dma collection buffer enable (dcb_en) ?r/w. 1 = enables dma collection buffer (dcb) for lpc i/f and pc/pci dma. 0 = dcb disabled. 1 delayed transaction enable (dte) ?r/w. 1 = ich2 enables delayed transactions for internal register, fwh, and lpc interface accesses. 0 = delayed transactions disabled. 0 positive decode enable (pos_dec_en) ?r/w. 1 = enables ich2 to only perform positive decode on the pci bus. 0 = the ich2 performs subtractive decode on the pci bus and forward the cycles to lpc interface if not to an internal register or other known target on the lpc interface. accesses to internal registers and to known lpc interface devices are still be positively decoded. bit description 82801BA ich2 and 82801BAm ich2-m datasheet 9-13 lpc interface bridge registers (d31:f0) 9.1.23 gen_sts?general status (lpc i/f?d31:f0) offset address: d4h?d7h attribute: r/w default value: 00000f0xh size: 32-bit lockable: no power well: core(0:7), rtc (8:15) bit description 31:14 reserved. 13 top_swap ?r/w. 1 = ich2 will invert a16 for cycles targeting fwh bios space (does not affect accesses to fwh feature space). 0 = ich2 will not invert a16. this bit is cleared by rtcrst# assertion, but not by any other type of reset. 12 cpu bist enable (cpu_bist_en) ?r/w. this bit is in the resume well and is reset by rsmrst# (not in the rtc well and not reset by rtest#). 1 = the init# signal is driven active when cpurst# is active. init# goes inactive with the same timings as the other processor interface signals (hold time after cpurst# inactive). note that cpurst# is generated by the memory controller hub; however, the ich2 has a hub interface special cycle that allows the ich2 to control the assertion/deassertion of cpurst#. 0 = disable. 11:8 processor frequency strap (freq_strap[3:0]) ?r/w. these bits determine the internal frequency multiplier of the processor. these bits can be reset to 1111 based on an external pin strap or via the rtcrst# input signal. software must program this field based on the processor?s specified frequency. these bits are in the rtc well. this field is only writeable when safe_mode (bit 2) is cleared to 0. safe_mode is only cleared by a pwrok rising edge. 7:3 reserved 2 safe_mode ?ro. 1 = ich2 sampled ac_sdout high on the rising edge of pwrok. ich2 will force freq_strap[3:0] bits to all 1s (safe mode multiplier). 0 = ich2 sampled ac_sdout low on the rising edge of pwrok. 1 no_reboot ?r/w (special). 1 = ich2 will disable the tco timer system reboot feature. this bit is set either by hardware when spkr is sampled low on the rising edge of pwrok or by software writing a 1 to the bit. 0 = normal tco timer reboot functionality (reboot after 2nd tco time-out). note that this bit cannot be cleared while an external jumper is in place on the spkr signal. 0 reserved. lpc interface bridge registers (d31:f0) 9-14 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.24 rtc_conf?rtc configuration register (lpc i/f?d31:f0) offset address: d8h attribute: r/w default value: 00h size: 8-bit lockable: yes power well: core 9.1.25 com_dec?lpc i/f communication port decode ranges (lpc i/f?d31:f0) offset address: e0h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core bit description 7:5 reserved. 4 upper 128-byte lock (u128lock) ?r/w (special). 1 = lock reads and writes to bytes 38h?3fh in the upper 128 byte bank of the rtc cmos ram. write cycles to this range will have no effect and read cycles will not return any particular guaranteed value. this is a write once register that can only be reset by a hardware reset. 0 = access to these bytes in the upper cmos ram range have not been locked. 3 lower 128-byte lock (l128lock) ?r/w (special). 1 = locks reads and writes to bytes 38h?3fh in the lower 128 byte bank of the rtc cmos ram. write cycles to this range will have no effect and read cycles will not return any particular guaranteed value. this is a write once register that can only be reset by a hardware reset. 0 = access to these bytes in the lower cmos ram range have not been locked. 2 upper 128-byte enable (u128e) ?r/w. 1 = enables access to the upper 128 byte bank of rtc cmos ram. 0 = disable. 1:0 reserved. bit description 7 reserved 6:4 comb decode range ?r/w. this field determines which range to decode for the comb port. 000 = 3f8h?3ffh (com1) 001 = 2f8h?2ffh (com2) 010 = 220h?227h 011 = 228h?22fh 100 = 238h?23fh 101 = 2e8h?2efh (com4) 110 = 338h?33fh 111 = 3e8h?3efh (com3) 3 reserved 2:0 coma decode range ?r/w. this field determines which range to decode for the coma port. 000 = 3f8h?3ffh (com1) 001 = 2f8h?2ffh (com2) 010 = 220h?227h 011 = 228h?22fh 100 = 238h?23fh 101 = 2e8h?2efh (com4) 110 = 338h?33fh 111 = 3e8h?3efh (com3) 82801BA ich2 and 82801BAm ich2-m datasheet 9-15 lpc interface bridge registers (d31:f0) 9.1.26 fdd/lpt_dec?lpc i/f fdd & lpt decode ranges (lpc i/f?d31:f0) offset address: e1h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 9.1.27 snd_dec?lpc i/f sound decode ranges (lpc i/f?d31:f0) offset address: e2h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core bit description 7:5 reserved 4 fdd decode range ?r/w. determines which range to decode for the fdd port 0 = 3f0h?3f5h, 3f7h (primary) 1 = 370h?2ffh (secondary) 3:2 reserved 1:0 lpt decode range ?r/w. this field determines which range to decode for the lpt port. 00 = 378h?37fh and 778h?77fh 01 = 278h?27fh (port 279h is read only) and 678h?67fh 10 = 3bch?3beh and 7bch?7beh 11 = reserved bit description 7:6 reserved 5:4 mss decode range ?r/w. this field determines which range to decode for the microsoft* sound system (mss). 00 = 530h?537h 01 = 604h?60bh 10 = e80h?e87h 11 = f40h?f47h 3 midi decode range ?r/w. this bit determines which range to decode for the midi port. 0 = 330h?331h 1 = 300h?301h 2 reserved 1:0 sb16 decode range ?r/w. this field determines which range to decode for the sound blaster 16 (sb16) port. 00 = 220h?233h 01 = 240h?253h 10 = 260h?273h 11 = 280h?293h lpc interface bridge registers (d31:f0) 9-16 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.28 fwh_dec_en1?fwh decode enable 1 register (lpc i/f?d31:f0) offset address: e3h attribute: r/w default value: ffh size: 8 bits this register determines which memory ranges will be decoded on the pci bus and forwarded to the fwh. the ich2 will subtractively decode cycles on pci unless pos_dec_en is set to 1. bit description 7 fwh address range enable (fwh_f8_en) ?ro. enables decoding two 512 kb fwh memory ranges and one 128 kb memory range. 1 = enable the following ranges for the fwh fff80000h?ffffffffh ffb80000h?ffbfffffh 000e0000h?000fffffh 6 fwh address range enable (fwh_f0_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh: fff00000h?fff7ffffh ffb00000h?ffb7ffffh 5 fwh address range enable (fwh_e8_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh: ffe80000h?ffeffffh ffa80000h?ffafffffh 4 fwh address range enable (fwh_e0_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh: ffe00000h?ffe7ffffh ffa00000h?ffa7ffffh 3 fwh address range enable (fwh_d8_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ffd80000h?ffdfffffh ff980000h?ff9fffffh 2 fwh address range enable (fwh_d0_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ffd00000h?ffd7ffffh ff900000h?ff97ffffh 1 fwh address range enable (fwh_c8_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ffc80000h?ffcfffffh ff880000h?ff8fffffh 0 fwh address range enable (fwh_c0_en) ?r/w. enables decoding two 512 kb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ffc00000h?ffc7ffffh ff800000h?ff87ffffh 82801BA ich2 and 82801BAm ich2-m datasheet 9-17 lpc interface bridge registers (d31:f0) 9.1.29 gen1_dec?lpc i/f generic decode range 1 (lpc i/f?d31:f0) offset address: e4h?e5h attribute: r/w default value: 00h size: 16-bit lockable: yes power well: core 9.1.30 lpc_en?lpc i/f enables (lpc i/f?d31:f0) offset address: e6h?e7h attribute: r/w default value: 00h size: 16-bit lockable: yes power well: core bit description 15:7 generic i/o decode range 1 base address (gen1_base) ?r/w. this address is aligned on a 128-byte boundary, and must have address lines 31:16 as 0. note that this generic decode is for i/o addresses only, not memory addresses. the size of this range is 128 bytes. 6:1 reserved. 0 generic decode range 1 enable (gen1_en) ?r/w. 0 = disable. 1 = enable the gen1 i/o range to be forwarded to the lpc i/f bit description 15:14 reserved 13 microcontroller address range enable (cnf2_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 4eh and 4fh to the lpc interface. this range is used for a microcontroller. 12 super i/o address range enable (cnf1_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 2eh and 2fh to the lpc interface. this range is used for super i/o devices. 11 microcontroller address range enable (mc_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 62h and 66h to the lpc interface. this range is used for a microcontroller. 10 microcontroller address range enable (kbc_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 60h and 64h to the lpc interface. this range is used for a microcontroller. 9 game port address range enable (gameh_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 208h to 20fh to the lpc interface. this range is used for a gameport. 8 game port address range enable (gamel_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 200h to 207h to the lpc interface. this range is used for a gameport. lpc interface bridge registers (d31:f0) 9-18 82801BA ich2 and 82801BAm ich2-m datasheet 7 adlib address range enable (adlib_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the i/o locations 388h?38bh to the lpc interface. 6 mss address range enable (mss_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the mss range to the lpc interface. this range is selected in the lpc_sound decode range register. 5 midi address range enable (midi_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the midi range to the lpc interface. this range is selected in the lpc_sound decode range register. 4 sound blaster address range enable (sb16_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the sb16 range to the lpc interface. this range is selected in the lpc_sound decode range register. 3 fdd address range enable (fdd_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the fdd range to the lpc interface. this range is selected in the lpc_fdd/lpt decode range register. 2 lpt address range enable (lpt_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the lpt range to the lpc interface. this range is selected in the lpc_fdd/lpt decode range register. 1 com b address range enable (comb_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the comb range to the lpc interface. this range is selected in the lpc_com decode range register. 0 com a address range enable (coma_lpc_en) ?r/w. 0 = disable. 1 = enables the decoding of the coma range to the lpc interface. this range is selected in the lpc_com decode range register. bit description 82801BA ich2 and 82801BAm ich2-m datasheet 9-19 lpc interface bridge registers (d31:f0) 9.1.31 fwh_sel1?fwh select 1 register (lpc i/f?d31:f0) offset address: e8h attribute: r/w default value: 00112233h size: 32 bits bit description 31:28 fwh address range select (fwh_f8_idsel) ?ro. idsel for two 512 kb fwh memory ranges and one 128kb memory range. this field is fixed at 0000. the idsel in this field addresses the following memory ranges: fff8 0000h?ffff ffffh ffb8 0000h?ffbf ffffh 000e 0000h?000f ffffh 27:24 fwh address range select (fwh_f0_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: fff0 0000h?fff7 ffffh ffb0 0000h?ffb7 ffffh 23:20 fwh address range select (fwh_e8_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffe8 0000h?ffef ffffh ffa8 0000h?ffaf ffffh 19:16 fwh address range select (fwh_e0_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffe0 0000h?ffe7 ffffh ffa0 0000h?ffa7 ffffh 15:12 fwh address range select (fwh_d8_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffd8 0000h?ffdf ffffh ff98 0000h?ff9f ffffh 11:8 fwh address range select (fwh_d0_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffd0 0000h?ffd7 ffffh ff90 0000h?ff97 ffffh 7:4 fwh address range select (fwh_c8_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffc8 0000h?ffcf ffffh ff88 0000h?ff8f ffffh 3:0 fwh address range select (fwh_c0_idsel) ?r/w. idsel for two 512 kb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ffc0 0000h?ffc7 ffffh ff80 0000h?ff87 ffffh lpc interface bridge registers (d31:f0) 9-20 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.32 gen2_dec?lpc i/f generic decode range 2 (lpc i/f?d31:f0) offset address: ech?edh attribute: r/w default value: 00h size: 16-bit lockable: yes power well: core 9.1.33 fwh_sel2?fwh select 2 register (lpc i/f?d31:f0) offset address: eeh?efh attribute: r/w default value: 4567h size: 32 bits bit description 15:4 generic i/o decode range 2 base address (gen2_base) ?r/w. this address is aligned on a 64-byte boundary and must have address lines 31:16 as 0. note that this generic decode is for i/o addresses only; not memory addresses. the size of this range is 16 bytes. 3:1 reserved. read as 0 0 generic i/o decode range 2 enable (gen2_en) ?r/w. 0 = disable. 1 = accesses to the gen2 i/o range will be forwarded to the lpc interface. bit description 15:12 fwh address range select (fwh_70_idsel) ?r/w. idsel for two 1 mb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ff70 0000h?ff7f ffffh ff30 0000h?ff3f ffffh 11:8 fwh address range select (fwh_60_idsel) ?r/w. idsel for two 1 mb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ff60 0000h?ff6f ffffh ff20 0000h?ff2f ffffh 7:4 fwh address range select (fwh_50_idsel) ?r/w. idsel for two 1 mb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ff50 0000h?ff5f ffffh ff10 0000h?ff1f ffffh 3:0 fwh address range select (fwh_40_idsel) ?r/w. idsel for two 1 mb fwh memory ranges. the idsel programmed in this field addresses the following memory ranges: ff40 0000h?ff4f ffffh ff00 0000h?ff0f ffffh 82801BA ich2 and 82801BAm ich2-m datasheet 9-21 lpc interface bridge registers (d31:f0) 9.1.34 fwh_dec_en2?fwh decode enable 2 register (lpc i/f?d31:f0) offset address: f0h attribute: r/w default value: 0fh size: 8 bits this register determines which memory ranges are decoded on the pci bus and forwarded to the fwh. the ich2 subtractively decodes cycles on pci unless pos_dec_en is set to 1. bit description 7:4 reserved. 3 fwh address range enable (fwh_70_en) ?r/w. enables decoding two 1 mb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ff70 0000h?ff7f ffffh ff30 0000h?ff3f ffffh 2 fwh address range enable (fwh_60_en) ?r/w. enables decoding two 1 mb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ff60 0000h?ff6f ffffh ff20 0000h?ff2f ffffh 1 fwh address range enable (fwh_50_en) ?r/w. enables decoding two 1 mb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ff50 0000h?ff5f ffffh ff10 0000h?ff1f ffffh 0 fwh address range enable (fwh_40_en) ?r/w. enables decoding two 1 mb fwh memory ranges. 0 = disable. 1 = enable the following ranges for the fwh ff40 0000h?ff4f ffffh ff00 0000h?ff0f ffffh lpc interface bridge registers (d31:f0) 9-22 82801BA ich2 and 82801BAm ich2-m datasheet 9.1.35 func_dis?function disable register (lpc i/f?d31:f0) offset address: f2h attribute: r/w default value: 00h size: 16-bit lockable: no power well: core bit description 15:9 reserved 8 smbus for bios (smb_for_bios) ?r/w. this bit is used in conjunction with bit 3 in this register. 0 = no effect. 1 = allows the smbus i/o space to be accessible by software when bit 3 in this register is set. the pci configuration space is hidden in this case. note that if bit 3 is set alone, the decode of both smbus pci configuration and i/o space will be disabled. 7 reserved 6 ac?97 modem disable (f6_disable) ?r/w. software sets this bit to disable the ac?97 modem controller function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = ac?97 modem is enabled 1 = ac?97 modem is disabled 5 ac?97 audio controller disable (f5_disable) ?r/w. software sets this bit to disable the ac?97 audio controller function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = ac?97 audio controller is enabled 1 = ac?97 audio controller is disabled 4 usb controller 2 disable (f4_disable) ?r/w. software sets this bit to disable the usb controller #2 function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = usb controller #2 is enabled 1 = usb controller #2 is disabled 3 smbus controller disable (f3_disable) ?r/w. software sets this bit to disable the smbus host controller function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = smbus controller is enabled 1 = smbus controller is disabled 2 usb controller 1 disable (f2_disable) ?r/w. software sets this bit to disable the usb controller #1 function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = usb controller #1 is enabled 1 = usb controller #1 is disabled 1 ide controller disable (f1_disable) ?r/w. software sets this bit to disable the ide controller function. bios must not enable i/o or memory address space decode, interrupt generation or any other functionality for functions that are to be disabled. 0 = ide controller is enabled 1 = ide controller is disabled 0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 9-23 lpc interface bridge registers (d31:f0) 9.2 dma i/o registers table 9-2. dma registers port alias register name/function default type 00h 10h channel 0 dma base & current address register undefined r/w 01h 11h channel 0 dma base & current count register undefined r/w 02h 12h channel 1 dma base & current address register undefined r/w 03h 13h channel 1 dma base & current count register undefined r/w 04h 14h channel 2 dma base & current address register undefined r/w 05h 15h channel 2 dma base & current count register undefined r/w 06h 16h channel 3 dma base & current address register undefined r/w 07h 17h channel 3 dma base & current count register undefined r/w 08h 18h channel 0?3 dma command register undefined wo channel 0?3 dma status register undefined ro 0ah 1ah channel 0?3 dma write single mask register 000001xxb wo 0bh 1bh channel 0?3 dma channel mode register 000000xxb wo 0ch 1ch channel 0?3 dma clear byte pointer register undefined wo 0dh 1dh channel 0?3 dma master clear register undefined wo 0eh 1eh channel 0?3 dma clear mask register undefined wo 0fh 1fh channel 0?3 dma write all mask register 0fh r/w 80h 90h reserved page register undefined r/w 81h 91h channel 2 dma memory low page register undefined r/w 82h ? channel 3 dma memory low page register undefined r/w 83h 93h channel 1 dma memory low page register undefined r/w 84h?86h 94h?96h reserved page registers undefined r/w 87h 97h channel 0 dma memory low page register undefined r/w 88h 98h reserved page register undefined r/w 89h 99h channel 6 dma memory low page register undefined r/w 8ah 9ah channel 7 dma memory low page register undefined r/w 8bh 9bh channel 5 dma memory low page register undefined r/w 8ch?8eh 9ch?9eh reserved page registers undefined r/w 8fh 9fh refresh low page register undefined r/w c0h c1h channel 4 dma base & current address register undefined r/w c2h c3h channel 4 dma base & current count register undefined r/w c4h c5h channel 5 dma base & current address register undefined r/w c6h c7h channel 5 dma base & current count register undefined r/w c8h c9h channel 6 dma base & current address register undefined r/w cah cbh channel 6 dma base & current count register undefined r/w cch cdh channel 7 dma base & current address register undefined r/w lpc interface bridge registers (d31:f0) 9-24 82801BA ich2 and 82801BAm ich2-m datasheet 9.2.1 dmabase_ca?dma base and current address registers i/o address: ch. #0 = 00h; ch. #1 = 02h attribute: ro ch. #2 = 04h; ch. #3 = 06h size: 16-bit (per channel), ch. #5 = c4h ch. #6 = c8h but accessed in two 8-bit ch. #7 = cch; quantities default value: undef lockable: no power well: core ceh cfh channel 7 dma base & current count register undefined r/w d0h d1h channel 4?7 dma command register undefined wo channel 4?7 dma status register undefined ro d4h d5h channel 4?7 dma write single mask register 000001xxb wo d6h d7h channel 4?7 dma channel mode register 000000xxb wo d8h d9h channel 4?7 dma clear byte pointer register undefined wo dah dbh channel 4?7 dma master clear register undefined wo dch ddh channel 4?7 dma clear mask register undefined wo deh dfh channel 4?7 dma write all mask register 0fh r/w table 9-2. dma registers (continued) port alias register name/function default type bit description 15:0 base and current address ?r/w. this register determines the address for the transfers to be performed. the address specified points to two separate registers. on writes, the value is stored in the base address register and copied to the current address register. on reads, the value is returned from the current address register. the address increments/decrements in the current address register after each transfer, depending on the mode of the transfer. if the channel is in auto-initialize mode, the current address register will be reloaded from the base address register after a terminal count is generated. for transfers to/from a 16-bit slave (channels 5?7), the address is shifted left one bit location. bit 15 will be shifted out. therefore, if bit 15 was a 1, it will be lost. the register is accessed in 8 bit quantities. the byte is pointed to by the current byte pointer flip/flop. before accessing an address register, the byte pointer flip/flop should be cleared to ensure that the low byte is accessed first. 82801BA ich2 and 82801BAm ich2-m datasheet 9-25 lpc interface bridge registers (d31:f0) 9.2.2 dmabase_cc?dma base and current count registers i/o address: ch. #0 = 01h; ch. #1 = 03h attribute: r/w ch. #2 = 05h; ch. #3 = 07h size: 16-bit (per channel), ch. #5 = c6h; ch. #6 = cah but accessed in two 8-bit ch. #7 = ceh; quantities default value: undefined lockable: no power well: core 9.2.3 dmamem_lp?dma memory low page registers i/o address: ch. #0 = 87h; ch. #1 = 83h ch. #2 = 81h; ch. #3 = 82h ch. #5 = 8bh; ch. #6 = 89h ch. #7 = 8ah; attribute: r/w default value: undefined size: 8-bit lockable: no power well: core bit description 15:0 base and current count ?r/w. this register determines the number of transfers to be performed. the address specified points to two separate registers. on writes the value is stored in the base count register and copied to the current count register. on reads the value is returned from the current count register. the actual number of transfers is one more than the number programmed in the base count register (i.e., programming a count of 4h results in 5 transfers). the count is decrements in the current count register after each transfer. when the value in the register rolls from zero to ffffh, a terminal count is generated. if the channel is in auto-initialize mode, the current count register will be reloaded from the base count register after a terminal count is generated. for transfers to/from an 8-bit slave (channels 0?3), the count register indicates the number of bytes to be transferred. for transfers to/from a 16-bit slave (channels 5?7), the count register indicates the number of words to be transferred. the register is accessed in 8 bit quantities. the byte is pointed to by the current byte pointer flip/flop. before accessing a count register, the byte pointer flip/flop should be cleared to ensure that the low byte is accessed first. bit description 7:0 dma low page (isa address bits [23:16]) ?r/w. this register works in conjunction with the dma controller's current address register to define the complete 24-bit address for the dma channel. this register remains static throughout the dma transfer. lpc interface bridge registers (d31:f0) 9-26 82801BA ich2 and 82801BAm ich2-m datasheet 9.2.4 dmacmd?dma command register i/o address: ch. #0?3 = 08h; ch. #4?7 = d0h attribute: wo default value: undefined size: 8-bit lockable: no power well: core 9.2.5 dmasts?dma status register i/o address: ch. #0?3 = 08h; ch. #4?7 = d0h attribute: ro default value: undefined size: 8-bit lockable: no power well: core bit description 7:5 reserved. must be 0. 4 dma group arbitration priority ?wo. each channel group is individually assigned either fixed or rotating arbitration priority. at part reset, each group is initialized in fixed priority. 0 = fixed priority to the channel group 1 = rotating priority to the group. 3 reserved. must be 0 2 dma channel group enable ?wo. both channel groups are enabled following part reset. 0 = enable the dma channel group. 1 = disable. disabling channel group 4?7 also disables channel group 0?3, which is cascaded through channel 4. 1:0 reserved. must be 0. bit description 7:4 channel request status ?ro. when a valid dma request is pending for a channel, the corresponding bit is set to 1. when a dma request is not pending for a particular channel, the corresponding bit is set to 0. the source of the dreq may be hardware or a software request. note that channel 4 is the cascade channel, so the request status of channel 4 is a logical or of the request status for channels 0 through 3. 4 = channel 0 5 = channel 1 (5) 6 = channel 2 (6) 7 = channel 3 (7) 3:0 channel terminal count status ?ro. when a channel reaches terminal count (tc), its status bit is set to 1. if tc has not been reached, the status bit is set to 0. channel 4 is programmed for cascade, so the tc bit response for channel 4 is irrelevant. 0 = channel 0 1 = channel 1 (5) 2 = channel 2 (6) 3 = channel 3 (7) 82801BA ich2 and 82801BAm ich2-m datasheet 9-27 lpc interface bridge registers (d31:f0) 9.2.6 dma_wrsmsk?dma write single mask register i/o address: ch. #0?3 = 0ah; ch. #4?7 = d4h attribute: wo default value: 0000 01xx size: 8-bit lockable: no power well: core 9.2.7 dmach_mode?dma channel mode register i/o address: ch. #0?3 = 0bh; ch. #4?7 = d6h attribute: wo default value: 0000 00xx size: 8-bit lockable: no power well: core bit description 7:3 reserved. must be 0. 2 channel mask select ?wo. 0 = enable dreq for the selected channel. the channel is selected through bits [1:0]. therefore, only one channel can be masked / unmasked at a time. 1 = disable dreq for the selected channel. 1:0 dma channel select ?wo. these bits select the dma channel mode register to program. 00 = channel 0 (4) 01 = channel 1 (5) 10 = channel 2 (6) 11 = channel 3 (7) bit description 7:6 dma transfer mode ?wo. each dma channel can be programmed in one of four different modes: 00 = demand mode 01 = single mode 10 = reserved 11 = cascade mode 5 address increment/decrement select ?wo. this bit controls address increment/decrement during dma transfers. 0 = address increment. (default after part reset or master clear) 1 = address decrement. 4 autoinitialize enable ?wo. 0 = autoinitialize feature is disabled and dma transfers terminate on a terminal count. a part reset or master clear disables autoinitialization. 1 = dma restores the base address and count registers to the current registers following a terminal count (tc). 3:2 dma transfer type ?wo. these bits represent the direction of the dma transfer. when the channel is programmed for cascade mode, (bits[7:6] = ?11?) the transfer type is irrelevant. 00 = verify - no i/o or memory strobes generated 01 = write - data transferred from the i/o devices to memory 10 = read - data transferred from memory to the i/o device 11 = illegal 1:0 dma channel select ?wo. these bits select the dma channel mode register that will be written by bits [7:2]. 00 = channel 0 (4) 01 = channel 1 (5) 10 = channel 2 (6) 11 = channel 3 (7) lpc interface bridge registers (d31:f0) 9-28 82801BA ich2 and 82801BAm ich2-m datasheet 9.2.8 dma clear byte pointer register i/o address: ch. #0?3 = 0ch; ch. #4?7 = d8h attribute: wo default value: xxxx xxxx size: 8-bit lockable: no power well: core 9.2.9 dma master clear register i/o address: ch. #0?3 = 0dh; ch. #4?7 = dah attribute: wo default value: xxxx xxxx size: 8-bit 9.2.10 dma_clmsk?dma clear mask register i/o address: ch. #0?3 = 0eh; ch. #4?7 = dch attribute: wo default value: xxxx xxxx size: 8-bit lockable: no power well: core bit description 7:0 clear byte pointer ?wo. no specific pattern. command enabled with a write to the i/o port address. writing to this register initializes the byte pointer flip/flop to a known state. it clears the internal latch used to address the upper or lower byte of the 16-bit address and word count registers. the latch is also cleared by part reset and by the master clear command. this command precedes the first access to a 16-bit dma controller register. the first access to a 16 bit register will then access the significant byte, and the second access automatically accesses the most significant byte. bit description 7:0 master clear ?wo. no specific pattern. enabled with a write to the port. this has the same effect as the hardware reset. the command, status, request, and byte pointer flip/flop registers are cleared and the mask register is set. bit description 7:0 clear mask register ?wo. no specific pattern. command enabled with a write to the port. 82801BA ich2 and 82801BAm ich2-m datasheet 9-29 lpc interface bridge registers (d31:f0) 9.2.11 dma_wrmsk?dma write all mask register i/o address: ch. #0?3 = 0fh; ch. #4?7 = deh attribute: r/w default value: 0000 1111 size: 8-bit lockable: no power well: core bit description 7:4 reserved. must be 0. 3:0 channel mask bits ?r/w. this register permits all four channels to be simultaneously enabled/ disabled instead of enabling/disabling each channel individually, as is the case with the mask register - write single mask bit. in addition, this register has a read path to allow the status of the channel mask bits to be read. a channel's mask bit is automatically set to 1 when the current byte/ word count register reaches terminal count (unless the channel is in auto-initialization mode). setting the bit(s) to a 1 disables the corresponding dreq(s). setting the bit(s) to a 0 enables the corresponding dreq(s). bits [3:0] are set to 1 upon part reset or master clear. when read, bits [3:0] indicate the dma channel [3:0] ([7:4]) mask status. bit 0 = channel 0 (4) 1 = masked, 0 = not masked bit 1 = channel 1 (5) 1 = masked, 0 = not masked bit 2 = channel 2 (6) 1 = masked, 0 = not masked bit 3 = channel 3 (7) 1 = masked, 0 = not masked note: disabling channel 4 also disables channels 0?3 due to the cascade of channels 0?3 through channel 4. lpc interface bridge registers (d31:f0) 9-30 82801BA ich2 and 82801BAm ich2-m datasheet 9.3 timer i/o registers 9.3.1 tcw?timer control word register i/o address: 43h attribute: wo default value: all bits undefined size: 8 bits this register is programmed prior to any counter being accessed to specify counter modes. following part reset, the control words for each register are undefined and each counter output is 0. each timer must be programmed to bring it into a known state. port aliases register name/function default value type 40h 50h counter 0 interval time status byte format 0xxxxxxxb ro counter 0 counter access port register undefined r/w 41h 51h counter 1 interval time status byte format 0xxxxxxxb ro counter 1 counter access port register undefined r/w 42h 52h counter 2 interval time status byte format 0xxxxxxxb ro counter 2 counter access port register undefined r/w 43h 53h timer control word register undefined wo timer control word register read back xxxxxxx0b wo counter latch command x0h wo bit description 7:6 counter select ?wo. the counter selection bits select the counter the control word acts upon as shown below. the read back command is selected when bits[7:6] are both 1. 00 = counter 0 select 01 = counter 1 select 10 = counter 2 select 11 = read back command 5:4 read/write select ?wo. these bits are the read/write control bits. the actual counter programming is done through the counter port (40h for counter 0, 41h for counter 1, and 42h for counter 2). 00 = counter latch command 01 = read/write least significant byte (lsb) 10 = read/write most significant byte (msb) 11 = read/write lsb then msb 3:1 counter mode selection ?wo. these bits select one of six possible modes of operation for the selected counter. 000 = mode 0 out signal on end of count (=0) 001 = mode 1 hardware retriggerable one-shot x10 = mode 2 rate generator (divide by n counter) x11 = mode 3 square wave output 100 = mode 4 software triggered strobe 101 = mode 5 hardware triggered strobe 0 binary/bcd countdown select ?wo. 0 = binary countdown is used. the largest possible binary count is 2 16 1 = binary coded decimal (bcd) count is used. the largest possible bcd count is 10 4 82801BA ich2 and 82801BAm ich2-m datasheet 9-31 lpc interface bridge registers (d31:f0) there are two special commands that can be issued to the counters through this register, the read back command and the counter latch command. when these commands are chosen, several bits within this register are redefined. these register formats are described below. 9.3.1.1 rdbk_cmd?read back command the read back command is used to determine the count value, programmed mode, and current states of the out pin and null count flag of the selected counter or counters. status and/or count may be latched in any or all of the counters by selecting the counter during the register write. the count and status remain latched until read, and further latch commands are ignored until the count is read. both count and status of the selected counters may be latched simultaneously by setting both bit 5 and bit 4 to 0. if both are latched, the first read operation from that counter returns the latched status. the next one or two reads, depending on whether the counter is programmed for one or two byte counts, returns the latched count. subsequent reads return an unlatched count. 9.3.1.2 ltch_cmd?counter latch command the counter latch command latches the current count value. this command is used to insure that the count read from the counter is accurate. the count value is then read from each counter's count register through the counter ports access ports register (40h for counter 0, 41h for counter 1, and 42h for counter 2). the count must be read according to the programmed format (i.e., if the counter is programmed for two byte counts, two bytes must be read). the two bytes do not have to be read one right after the other (read, write, or programming operations for other counters may be inserted between the reads). if a counter is latched once and then latched again before the count is read, the second counter latch command is ignored. bit description 7:6 read back command. this field must be ?11? to select the read back command. 5 latch count of selected counters. 0 = current count value of the selected counters will be latched 1 = current count will not be latched 4 latch status of selected counters. 0 = status of the selected counters will be latched 1 = status will not be latched 3 counter 2 select. 1 = counter 2 count and/or status will be latched 2 counter 1 select. 1 = counter 1 count and/or status will be latched 1 counter 0 select. 1 = counter 0 count and/or status will be latched. 0 reserved. must be 0. bit description 7:6 counter selection. these bits select the counter for latching. if ?11? is written, then the write is interpreted as a read back command. 00 = counter 0 01 = counter 1 10 = counter 2 5:4 counter latch command. 00 = selects the counter latch command. 3:0 reserved. must be 0. lpc interface bridge registers (d31:f0) 9-32 82801BA ich2 and 82801BAm ich2-m datasheet 9.3.2 sbyte_fmt?interval timer status byte format register i/o address: counter 0 = 40h, counter 1 = 41h, attribute: ro counter 2 = 42h size: 8 bits per counter default value: bits[6:0] undefined, bit 7=0 each counter's status byte can be read following a read back command. if latch status is chosen (bit 4=0, read back command) as a read back option for a given counter, the next read from the counter's counter access ports register (40h for counter 0, 41h for counter 1, and 42h for counter 2) returns the status byte. the status byte returns the following: 9.3.3 counter access ports register i/o address: counter 0 ?40h, counter 1 ?41h, attribute: r/w counter 2?42h default value: all bits undefined size: 8 bit bit description 7 counter out pin state ?ro. 0 = out pin of the counter is also a 0. 1 = out pin of the counter is also a 1. 6 count register status ?ro. this bit indicates when the last count written to the count register (cr) has been loaded into the counting element (ce). the exact time this happens depends on the counter mode, but until the count is loaded into the counting element (ce), the count value will be incorrect. 0 = count has been transferred from cr to ce and is available for reading. 1 = null count. count has not been transferred from cr to ce and is not yet available for reading. 5:4 read/write selection status ?ro. these reflect the read/write selection made through bits[5:4] of the control register. the binary codes returned during the status read match the codes used to program the counter read/write selection. 00 = counter latch command 01 = read/write least significant byte (lsb) 10 = read/write most significant byte (msb) 11 = read/write lsb then msb 3:1 mode selection status ?ro. these bits return the counter mode programming. the binary code returned matches the code used to program the counter mode, as listed under the bit function above. 000 = mode 0 out signal on end of count (=0) 001 = mode 1 hardware retriggerable one-shot x10 = mode 2 rate generator (divide by n counter) x11 = mode 3 square wave output 100 = mode 4 software triggered strobe 101 = mode 5 hardware triggered strobe 0 countdown type status ?ro. this bit reflects the current countdown type. 0 = binary countdown 1 = binary coded decimal (bcd) countdown. bit description 7:0 counter port ?r/w. each counter port address is used to program the 16-bit count register. the order of programming (either lsb only, msb only, or lsb then msb) is defined with the interval counter control register at port 43h. the counter port is also used to read the current count from the count register, and return the status of the counter programming following a read back command. 82801BA ich2 and 82801BAm ich2-m datasheet 9-33 lpc interface bridge registers (d31:f0) 9.4 8259 interrupt controller (pic) registers 9.4.1 interrupt controller i/o map the interrupt controller registers are located at 20h and 21h for the master controller (irq[0:7]), and at a0h and a1h for the slave controller (irq[8:13]). these registers have multiple functions depending on the data written to them. table 9-3 lists the different register possibilities for each address. table 9-3. pic registers port aliases register name/function default value type 20h 24h, 28h, 2ch, 30h, 34h, 38h, 3ch master pic icw1 init. cmd word 1 register undefined wo master pic ocw2 op ctrl word 2 register 001xxxxxb wo master pic ocw3 op ctrl word 3 register x01xxx10b r/w 21h 25h, 29h, 2dh, 31h, 35h, 39h, 3dh master pic icw2 init. cmd word 2 register undefined wo master pic icw3 init. cmd word 3 register undefined wo master pic icw4 init. cmd word 4 register 01h wo master pic ocw1 op ctrl word 1 register 00h r/w a0h a4h, a8h, ach, b0h, b4h, b8h, bch slave pic icw1 init. cmd word 1 register undefined wo slave pic ocw2 op ctrl word 2 register 001xxxxxb wo slave pic ocw3 op ctrl word 3 register x01xxx10b r/w a1h a5h, a9h, adh, b1h, b5h, b9h, bdh slave pic icw2 init. cmd word 2 register undefined wo slave pic icw3 init. cmd word 3 register undefined wo slave pic icw4 init. cmd word 4 register 01h wo slave pic ocw1 op ctrl word 1 register 00h r/w 4d0h ? master pic edge/level triggered register 00h r/w 4d1h ? slave pic edge/level triggered register 00h r/w lpc interface bridge registers (d31:f0) 9-34 82801BA ich2 and 82801BAm ich2-m datasheet 9.4.2 icw1?initialization command word 1 register offset address: master controller?020h attribute: wo slave controller?0a0h size: 8 bit /controller default value: all bits undefined a write to initialization command word 1 starts the interrupt controller initialization sequence, during which the following occurs: 1. the interrupt mask register is cleared. 2. irq7 input is assigned priority 7. 3. the slave mode address is set to 7. 4. special mask mode is cleared and status read is set to irr. once this write occurs, the controller expects writes to icw2, icw3, and icw4 to complete the initialization sequence. bit description 7:5 icw/ocw select ?wo. these bits are mcs-85 specific, and not needed. 000 = should be programmed to ?000? 4 icw/ocw select ?wo. 1 = this bit must be a 1 to select icw1 and enable the icw2, icw3, and icw4 sequence. 3 edge/level bank select (ltim) ?wo. disabled. replaced by the edge/level triggered control registers (elcr). 2 adi?wo. 0 = ignored for the ich2. should be programmed to 0. 1 single or cascade (sngl) ?wo. 0 = must be programmed to a 0 to indicate two controllers operating in cascade mode. 0 icw4 write required (ic4) ?wo. 1 = this bit must be programmed to a 1 to indicate that icw4 needs to be programmed. 82801BA ich2 and 82801BAm ich2-m datasheet 9-35 lpc interface bridge registers (d31:f0) 9.4.3 icw2?initialization command word 2 register offset address: master controller?021h attribute: wo slave controller?0a1h size: 8 bit /controller default value: all bits undefined icw2 is used to initialize the interrupt controller with the five most significant bits of the interrupt vector address. the value programmed for bits[7:3] is used by the processor to define the base address in the interrupt vector table for the interrupt routines associated with each irq on the controller. typical isa icw2 values are 08h for the master controller and 70h for the slave controller. 9.4.4 icw3?master controller initialization command word 3 register offset address: 21h attribute: wo default value: all bits undefined size: 8 bits bit description 7:3 interrupt vector base address ?wo. bits [7:3] define the base address in the interrupt vector table for the interrupt routines associated with each interrupt request level input. 2:0 interrupt request level ?wo. when writing icw2, these bits should all be 0. during an interrupt acknowledge cycle, these bits are programmed by the interrupt controller with the interrupt to be serviced. this is combined with bits [7:3] to form the interrupt vector driven onto the data bus during the second inta# cycle. the code is a three bit binary code: code master interrupt slave interrupt 000 irq0 irq8 001 irq1 irq9 010 irq2 irq10 011 irq3 irq11 100 irq4 irq12 101 irq5 irq13 110 irq6 irq14 111 irq7 irq15 bit description 7:3 0 = these bits must be programmed to zero. 2 cascaded interrupt controller irq connection ?wo. this bit indicates that the slave controller is cascaded on irq2. when irq8#?irq15 is asserted, it goes through the slave controller?s priority resolver. the slave controller?s intr output onto irq2. irq2 then goes through the master controller?s priority solver. if it wins, the intr signal is asserted to the processor, and the returning interrupt acknowledge returns the interrupt vector for the slave controller. 1 = this bit must always be programmed to a 1. 1:0 0 = these bits must be programmed to zero. lpc interface bridge registers (d31:f0) 9-36 82801BA ich2 and 82801BAm ich2-m datasheet 9.4.5 icw3?slave controller initialization command word 3 register offset address: a1h attribute: wo default value: all bits undefined size: 8 bits 9.4.6 icw4?initialization command word 4 register offset address: master controller?021h attribute: wo slave controller?0a1h size: 8 bits 9.4.7 ocw1?operational control word 1 (interrupt mask) register offset address: master controller?021h attribute: r/w slave controller?0a1h size: 8 bits default value: 00h bit description 7:3 0 = these bits must be programmed to zero. 2:0 slave identification code ?wo. these bits are compared against the slave identification code broadcast by the master controller from the trailing edge of the first internal inta# pulse to the trailing edge of the second internal inta# pulse. these bits must be programmed to 02h to match the code broadcast by the master controller. when 02h is broadcast by the master controller during the inta# sequence, the slave controller assumes responsibility for broadcasting the interrupt vector. bit description 7:5 0 = these bits must be programmed to zero. 4 special fully nested mode (sfnm) ?wo. 0 = should normally be disabled by writing a 0 to this bit. 1 = special fully nested mode is programmed. 3 buffered mode (buf) ?wo. 0 = must be programmed to 0 for the ich2. this is non-buffered mode. 2 master/slave in buffered mode ?wo. not used. 0 = should always be programmed to 0. 1 automatic end of interrupt (aeoi) ?wo. 0 = this bit should normally be programmed to 0. this is the normal end of interrupt. 1 = automatic end of interrupt (aeoi) mode is programmed. aeoi is discussed in section 5.7.4 . 0 microprocessor mode ?wo. 1 = must be programmed to 1 to indicate that the controller is operating in an intel architecture- based system. bit description 7:0 interrupt request mask ?r/w. when a 1 is written to any bit in this register, the corresponding irq line is masked. when a 0 is written to any bit in this register, the corresponding irq mask bit is cleared and interrupt requests will again be accepted by the controller. masking irq2 on the master controller will also mask the interrupt requests from the slave controller. 82801BA ich2 and 82801BAm ich2-m datasheet 9-37 lpc interface bridge registers (d31:f0) 9.4.8 ocw2?operational control word 2 register offset address: master controller?020h attribute: wo slave controller?0a0h size: 8 bits default value: bit[4:0]=undefined, bit[7:5]=001 following a part reset or icw initialization, the controller enters the fully nested mode of operation. non-specific eoi without rotation is the default. both rotation mode and specific eoi mode are disabled following initialization. bit description 7:5 rotate and eoi codes (r, sl, eoi) ?wo. these three bits control the rotate and end of interrupt modes and combinations of the two. 000 = rotate in auto eoi mode (clear) 001 = non-specific eoi command 010 = no operation 011 = specific eoi command 100 = rotate in auto eoi mode (set) 101 = rotate on non-specific eoi command 110 = *set priority command 111 = *rotate on specific eoi command *l0?l2 are used 4:3 ocw2 select ?wo. when selecting ocw2, bits 4:3 = ?00? 2:0 interrupt level select (l2, l1, l0) ?wo. l2, l1, and l0 determine the interrupt level acted upon when the sl bit is active. a simple binary code, outlined below, selects the channel for the command to act upon. when the sl bit is inactive, these bits do not have a defined function; programming l2, l1 and l0 to 0 is sufficient in this case. bits interrupt level bits interrupt level 000 irq0/8 100 irq4/12 001 irq1/9 101 irq5/13 010 irq2/10 110 irq6/14 011 irq3/11 111 irq7/15 lpc interface bridge registers (d31:f0) 9-38 82801BA ich2 and 82801BAm ich2-m datasheet 9.4.9 ocw3?operational control word 3 register offset address: master controller?020h attribute: wo slave controller?0a0h size: 8 bits default value: bit[6,0]=0, bit[7,4:2]=undefined, bit[5,1]=1 bit description 7 reserved. must be 0. 6 special mask mode (smm) ?wo. 1 = the special mask mode can be used by an interrupt service routine to dynamically alter the system priority structure while the routine is executing, through selective enabling/disabling of the other channel's mask bits. bit 5, the esmm bit, must be set for this bit to have any meaning. 5 enable special mask mode (esmm) ?wo. 0 = disable. the smm bit becomes a "don't care". 1 = enable the smm bit to set or reset the special mask mode. 4:3 ocw3 select ?wo. when selecting ocw3, bits 4:3 = ?01? 2 poll mode command ?wo. 0 = disable. poll command is not issued. 1 = enable. the next i/o read to the interrupt controller is treated as an interrupt acknowledge cycle. an encoded byte is driven onto the data bus, representing the highest priority level requesting service. 1:0 register read command ?wo. these bits provide control for reading the in-service register (isr) and the interrupt request register (irr). when bit 1=0, bit 0 will not affect the register read selection. when bit 1=1, bit 0 selects the register status returned following an ocw3 read. if bit 0=0, the irr will be read. if bit 0=1, the isr will be read. following icw initialization, the default ocw3 port address read will be "read irr". to retain the current selection (read isr or read irr), always write a 0 to bit 1 when programming this register. the selected register can be read repeatedly without reprogramming ocw3. to select a new status register, ocw3 must be reprogrammed prior to attempting the read. 00 = no action 01 = no action 10 = read irq register 11 = read is register 82801BA ich2 and 82801BAm ich2-m datasheet 9-39 lpc interface bridge registers (d31:f0) 9.4.10 elcr1?master controller edge/level triggered register offset address: 4d0h attribute: r/w default value: 00h size: 8 bits in edge mode, (bit[x] = 0), the interrupt is recognized by a low to high transition. in level mode (bit[x] = 1), the interrupt is recognized by a high level. the cascade channel, irq2, the heart beat timer (irq0), and the keyboard controller (irq1), cannot be put into level mode. bit description 7 irq7 ecl ?r/w. 0 = edge. 1 = level. 6 irq6 ecl ?r/w. 0 = edge. 1 = level. 5 irq5 ecl ?r/w. 0 = edge. 1 = level. 4 irq4 ecl ?r/w. 0 = edge. 1 = level. 3 irq3 ecl ?r/w. 0 = edge. 1 = level. 2:0 reserved. must be 0. lpc interface bridge registers (d31:f0) 9-40 82801BA ich2 and 82801BAm ich2-m datasheet 9.4.11 elcr2?slave controller edge/level triggered register offset address: 4d1h attribute: r/w default value: 00h size: 8 bits in edge mode (bit[x] = 0) the interrupt is recognized by a low-to-high transition. in level mode (bit[x] = 1) the interrupt is recognized by a high level. the real time clock interrupt (irq8#) and the floating point error interrupt (irq13) cannot be programmed for level mode. bit description 7 irq15 ecl ?r/w. 0 = edge. 1 = level. 6 irq14 ecl ?r/w. 0 = edge. 1 = level. 5 reserved. must be 0. 4 irq12 ecl ?r/w. 0 = edge. 1 = level. 3 irq11 ecl ?r/w. 0 = edge. 1 = level. 2 irq10 ecl ?r/w. 0 = edge. 1 = level. 1 irq9 ecl ?r/w. 0 = edge. 1 = level. 0 reserved. must be 0. 82801BA ich2 and 82801BAm ich2-m datasheet 9-41 lpc interface bridge registers (d31:f0) 9.5 advanced interrupt controller (apic) 9.5.1 apic register map the apic is accessed via an indirect addressing scheme. two registers are visible by software for manipulation of most of the apic registers. these registers are mapped into memory space. the registers are shown in table 9-4 . table 9-5 lists the registers which can be accessed within the apic via the index register. when accessing these registers, accesses must be done a dword at a time. for example, software should never access byte 2 from the data register before accessing bytes 0 and 1. the hardware will not attempt to recover from a bad programming model in this case. 9.5.2 ind?index register memory address fec0_0000h attribute: r/w default value: 00h size: 8 bits the index register will select which apic indirect register to be manipulated by software. the selector values for the indirect registers are listed in table 9-5 . software programs this register to select the desired apic internal register . table 9-4. apic direct registers address register size type fec0_0000h index register 8 bits r/w fec0_0010h data register 32 bits r/w feco_0020h irq pin assertion register 8 bits wo feco_0040h eoi register 8 bits wo table 9-5. apic indirect registers index register size type 00h id 32 bits r/w 01h version 32 bits ro 02h arbitration id 32 bits ro 03h boot configuration 32 bits r/w 03h?0fh reserved ro 10h ?11h redirection table 0 64 bits r/w 12h?13h redirection table 1 64 bits r/w ... ... ... ... 3eh?3fh redirection table 23 64 bits r/w 40h?ffh reserved ro bit description 7:0 apic index ?r/w. this is an 8 bit pointer into the i/o apic register table. lpc interface bridge registers (d31:f0) 9-42 82801BA ich2 and 82801BAm ich2-m datasheet 9.5.3 dat?data register memory address fec0_0010h attribute: r/w default value: 00000000h size: 32 bits this is a 32 bit register specifying the data to be read or written to the register pointed to by the index register. this register can only be accessed in dword quantities. 9.5.4 irqpa?irq pin assertion register memory address fec0_0020h attribute: wo default value: n/a size: 32 bits the irq pin assertion register is present to provide a mechanism to scale the number of interrupt inputs into the i/o apic without increasing the number of dedicated input pins. when a device that supports this interrupt assertion protocol requires interrupt service, that device will issue a write to this register. bits 4:0 written to this register contain the irq number for this interrupt. the only valid values are 0?23. bits 31:5 are ignored. to provide for future expansion, peripherals should always write a value of 0 for bits 31:5. see section 5.8.4 for more details on how pci devices will use this field. note: writes to this register are only allowed by the processor and by masters on the ich2?s pci bus. writes by devices on pci buses above the ich2 (e.g., a pci segment on a p64h) are not supported. bit description 7:0 apic data ?r/w. this is a 32 bit register for the data to be read or written to the apic indirect register pointed to by the index register. bit description 31:5 reserved. bits 31:5 are ignored. 4:0 irq number ?wo. bits 4:0 written to this register contain the irq number for this interrupt. the only valid values are 0?23. 82801BA ich2 and 82801BAm ich2-m datasheet 9-43 lpc interface bridge registers (d31:f0) 9.5.5 eoir?eoi register memory address fec0_0040h attribute: wo default value: n/a size: 32 bits the eoi register is present to provide a mechanism to maintain the level triggered semantics for level-triggered interrupts issued on the parallel bus. when a write is issued to this register, the i/o apic will check the lower 8 bits written to this register, and compare it with the vector field for each entry in the i/o redirection table. when a match is found, the remote_irr bit for that i/o redirection entry will be cleared. note: this is similar to what already occurs when the apic sees the eio message on the serial bus. note that if multiple i/o redirection entries, for any reason, assign the same vector for more than one interrupt input, each of those entries will have the remote_irr bit reset to 0. the interrupt which was prematurely reset will not be lost because if its input remained active when the remote_irr bit is cleared, the interrupt will be reissued and serviced at a later time. note: only bits 7:0 are actually used. bits 31:8 are ignored by the ich2. note: to provide for future expansion, the processor should always write a value of 0 to bits 31:8. 9.5.6 id?identification register index offset: 00h attribute: r/w default value: 00000000h size: 32 bits the apic id serves as a physical name of the apic. the apic bus arbitration id for the apic is derived from its i/o apic id. this register is reset to zero on power up reset. bit description 31:8 reserved. to provide for future expansion, the processor should always write a value of 0 to bits 31:8. 7:0 redirection entry clear ?wo. when a write is issued to this register, the i/o apic will check this field, and compare it with the vector field for each entry in the i/o redirection table. when a match is found, the remote_irr bit for that i/o redirection entry will be cleared. bit description 31:28 reserved. 27:24 apic id ?r/w. software must program this value before using the apic. 23:0 reserved. lpc interface bridge registers (d31:f0) 9-44 82801BA ich2 and 82801BAm ich2-m datasheet 9.5.7 ver?version register index offset: 01h attribute: ro default value: 00170002h size: 32 bits each i/o apic contains a hardwired version register that identifies different implementation of apic and their versions. the maximum redirection entry information also is in this register, to let software know how many interrupt are supported by this apic. 9.5.8 arbid?arbitration id register index offset: 02h attribute: ro default value: 00000000h size: 32 bits this register contains the bus arbitration priority for the apic. this register is loaded whenever the apic id register is loaded. a rotating priority scheme is used for apic bus arbitration. the winner of the arbitration becomes the lowest priority agent and assumes an arbitration id of 0. a 9.5.9 boot_config?boot configuration register index offset: 03h attribute: r/w default value: 00000000h size: 32 bits this register is used to control the interrupt delivery mechanism for the apic. a bit description 31:24 reserved. 23:16 maximum redirection entries ?ro. this is the entry number (0 being the lowest entry) of the highest entry in the redirection table. it is equal to the number of interrupt input pins minus one and is in the range 0 through 239. in the ich2 this field is hardwired to 17h to indicate 24 interrupts. 15 prq ?ro. this bit is set to 1 to indicate that this version of the i/o apic implements the irq assertion register and allows pci devices to write to it to cause interrupts. 14 :8 reserved. 7:0 version ?ro. this is a version number that identifies the implementation version. bit description 31:28 reserved. 27:24 i/o apic identification ?ro. this 4 bit field contains the i/o apic arbitration id. 23:0 reserved. bit description 31:1 reserved. 0 delivery type (dt) ?r/w. 0 = interrupt delivery mechanism is via the apic serial bus (default). 1 = interrupt delivery mechanism is a front-side bus message. 82801BA ich2 and 82801BAm ich2-m datasheet 9-45 lpc interface bridge registers (d31:f0) 9.5.10 redirection table index offset: 10h?11h (vector 0) through attribute: r/w 3e?3fh (vector 23) default value: bit 16?1, bits[15:12]=0. size: 64 bits each, (accessed as all other bits undefined two 32 bit quantities) the redirection table has a dedicated entry for each interrupt input pin. the information in the redirection table is used to translate the interrupt manifestation on the corresponding interrupt pin into an apic message. the apic will respond to an edge-triggered interrupt as long as the interrupt is held until after the acknowledge cycle has begun. once the interrupt is detected, a delivery status bit internally to the i/o apic is set. the state machine will step ahead and wait for an acknowledgment from the apic bus unit that the interrupt message was sent over the apic bus. only then will the i/o apic be able to recognize a new edge on that interrupt pin. that new edge will only result in a new invocation of the handler if its acceptance by the destination apic causes the interrupt request register bit to go from 0 to 1. (in other words, if the interrupt was not already pending at the destination.) bit description 63:56 destination ?r/w. if bit 11 of this entry is 0 [physical], then bits [59:56] specifies an apic id. if bit 11 of this entry is 1 [logical], then bits [63:56] specify the logical destination address of a set of processors. 55:17 reserved. 16 mask ?r/w. 0 = not masked: an edge or level on this interrupt pin results in the delivery of the interrupt to the destination. 1 = masked: interrupts are not delivered nor held pending. setting this bit after the interrupt is accepted by a local apic has no effect on that interrupt. this behavior is identical to the device withdrawing the interrupt before it is posted to the processor. it is software's responsibility to deal with the case where the mask bit is set after the interrupt message has been accepted by a local apic unit but before the interrupt is dispensed to the processor. 15 trigger mode ?r/w. this field indicates the type of signal on the interrupt pin that triggers an interrupt. 0 = edge triggered. 1 = level triggered. 14 remote irr ?r/w. this bit is used for level triggered interrupts; its meaning is undefined for edge triggered interrupts. 0 = reset when an eoi message is received from a local apic. 1 = set when local apic/s accept the level interrupt sent by the i/o apic. 13 interrupt input pin polarity ?r/w. this bit specifies the polarity of each interrupt signal connected to the interrupt pins. 0 = active high. 1 = active low. 12 delivery status ?ro. this field contains the current status of the delivery of this interrupt. writes to this bit have no effect. 0 = idle. no activity for this interrupt. 1 = pending. interrupt has been injected, but delivery is held up due to the apic bus being busy or the inability of the receiving apic unit to accept the interrupt at this time. 11 destination mode ?r/w. this field determines the interpretation of the destination field. 0 = physical. destination apic id is identified by bits [59:56]. 1 = logical. destinations are identified by matching bit [63:56] with the logical destination in the destination format register and logical destination register in each local apic. lpc interface bridge registers (d31:f0) 9-46 82801BA ich2 and 82801BAm ich2-m datasheet 10:8 delivery mode ?r/w. this field specifies how the apics listed in the destination field should act upon reception of this signal. certain delivery modes will only operate as intended when used in conjunction with a specific trigger mode. these encodings are: 000 = fixed. deliver the signal on the intr signal of all processor cores listed in the destination. trigger mode can be edge or level. 001 = lowest priority. deliver the signal on the intr signal of the processor core that is executing at the lowest priority among all the processors listed in the specified destination. trigger mode can be edge or level. 010 = smi (system management interrupt). requires the interrupt to be programmed as edge triggered. the vector information is ignored but must be programmed to all zeroes for future compatibility. 011 = reserved 100 = nmi. deliver the signal on the nmi signal of all processor cores listed in the destination. vector information is ignored. nmi is treated as an edge triggered interrupt even if it is programmed as level triggered. for proper operation this redirection table entry must be programmed to edge triggered. the nmi delivery mode does not set the rirr bit. once the interrupt is detected, it will be sent over the apic bus. if the redirection table is incorrectly set to level, the loop count will continue counting through the redirection table addresses. once the count for the nmi pin is reached again, the interrupt will be sent over the apic bus again. 101 = init. deliver the signal to all processor cores listed in the destination by asserting the init signal. all addressed local apics will assume their init state. init is always treated as an edge triggered interrupt even if programmed as level triggered. for proper operation this redirection table entry must be programmed to edge triggered. the init delivery mode does not set the rirr bit. once the interrupt is detected, it will be sent over the apic bus. if the redirection table is incorrectly set to level, the loop count will continue counting through the redirection table addresses. once the count for the init pin is reached again, the interrupt will be sent over the apic bus again 110 = reserved 111 = extint. deliver the signal to the intr signal of all processor cores listed in the destination as an interrupt that originated in an externally connected 8259a compatible interrupt controller. the inta cycle that corresponds to this extint delivery will be routed to the external controller that is expected to supply the vector. requires the interrupt to be programmed as edge triggered. 7:0 vector ?r/w. this field contains the interrupt vector for this interrupt. values range between 10h and feh. bit description 82801BA ich2 and 82801BAm ich2-m datasheet 9-47 lpc interface bridge registers (d31:f0) 9.6 real time clock registers 9.6.1 i/o register address map the rtc internal registers and ram are organized as two banks of 128 bytes each, called the standard and extended banks. the first 14 bytes of the standard bank contain the rtc time and date information along with four registers, a?d, that are used for configuration of the rtc. the extended bank contains a full 128 bytes of battery backed sram and will be accessible even when the rtc module is disabled (via the rtc configuration register). registers a?d do not physically exist in the ram. all data movement between the host processor and the real-time clock is done through registers mapped to the standard i/o space. the register map appears in table 9-6 . notes: 1. i/o locations 70h and 71h are the standard isa location for the real-time clock. the map for this bank is shown in table 9-7 . locations 72h and 73h are for accessing the extended ram. the extended ram bank is also accessed using an indexed scheme. i/o address 72h is used as the address pointer and i/o address 73h is used as the data register. index addresses above 127h are not valid. if the extended ram is not needed, it may be disabled. 2. software must preserve the value of bit 7 at i/o addresses 70h and 74h. when writing to these addresses, software must first read the value, and then write the same value for bit 7 during the sequential address write. 9.6.2 indexed registers the rtc contains two sets of indexed registers that are accessed using the two separate index and target registers (70h/71h or 72h/73h), as shown in table 9-7 . table 9-6. rtc i/o registers i/o locations if u128e bit = 0 function 70h and 74h also alias to 72h and 76h real-time clock (standard ram) index register 71h and 75h also alias to 73h and 77h real-time clock (standard ram) target register 72h and 76h extended ram index register (if enabled) 73h and 77h extended ram target register (if enabled) table 9-7. rtc (standard) ram bank index name index name 00h seconds 08h month 01h seconds alarm. 09h year 02h minutes 0ah register a 03h minutes alarm 0bh register b 04h hours 0ch register c 05h hours alarm 0dh register d 06h day of week 0eh?7fh 114 bytes of user ram 07h day of month lpc interface bridge registers (d31:f0) 9-48 82801BA ich2 and 82801BAm ich2-m datasheet 9.6.2.1 rtc_rega?register a rtc index: 0a attribute: r/w default value: undefined size: 8-bit lockable: no power well: rtc this register is used for general configuration of the rtc functions. none of the bits are affected by rsmrst# or any other ich2 reset signal. bit description 7 update in progress (uip) ?r/w. this bit may be monitored as a status flag. 0 = the update cycle will not start for at least 492us. the time, calendar, and alarm information in ram is always available when the uip bit is 0. 1 = the update is soon to occur or is in progress. 6:4 division chain select (dv[2:0]) ?r/w. these three bits control the divider chain for the oscillator, and are not affected by rsmrst# or any other reset signal. dv[2] corresponds to bit 6. 010 = normal operation 11x = divider reset 101 = bypass 15 stages (test mode only) 100 = bypass 10 stages (test mode only) 011 = bypass 5 stages (test mode only) 001 = invalid 000 = invalid 3:0 rs[3:0] rate select ?r/w. selects one of 13 taps of the 15 stage divider chain. the selected tap can generate a periodic interrupt if the pie bit is set in register b. otherwise this tap will set the pf flag of register c. if the periodic interrupt is not to be used, these bits should all be set to zero. rs3 corresponds to bit 3. 0000 = interrupt never toggles 1000 = 3.90625 ms 0001 = 3.90625 ms 1001 = 7.8125 ms 0010 = 7.8125 ms 1010 = 15.625 ms 0011 = 122.070 us 1011 = 31.25 ms 0100 = 244.141 us 1100 = 62.5 ms 0101 = 488.281 us 1101 = 125 ms 0110 = 976.5625 us 1110 = 250 ms 0111 = 1.953125 ms 1111= 500 ms 82801BA ich2 and 82801BAm ich2-m datasheet 9-49 lpc interface bridge registers (d31:f0) 9.6.2.2 rtc_regb?register b (general configuration) rtc index: 0bh attribute: r/w default value: u0u00uuu (u: undefined) size: 8-bit lockable: no power well: rtc bit description 7 update cycle inhibit (set) ?r/w. enables/inhibits the update cycles. this bit is not affected by rsmrst# nor any other reset signal. 0 = update cycle occurs normally once each second. 1 = a current update cycle will abort and subsequent update cycles will not occur until set is returned to zero. when set is one, the bios may initialize time and calendar bytes safely. 6 periodic interrupt enable (pie) ?r/w. this bit is cleared by rsmrst#, but not on any other reset. 0 = disable. 1 = allows an interrupt to occur with a time base set with the rs bits of register a. 5 alarm interrupt enable (aie) ?r/w. this bit is cleared by rsmrst#, but not on any other reset. 0 = disable. 1 = allows an interrupt to occur when the af is set by an alarm match from the update cycle. an alarm can occur once a second, one an hour, once a day, or one a month. 4 update-ended interrupt enable (uie) ?r/w. this bit is cleared by rsmrst#, but not on any other reset. 0 = disable. 1 = allows an interrupt to occur when the update cycle ends. 3 square wave enable (sqwe) ?r/w. this bit serves no function in the ich2. it is left in this register bank to provide compatibility with the motorola* 146818b. the ich2 has no sqw pin. this bit is cleared by rsmrst#, but not on any other reset. 2 data mode (dm) ?r/w. specifies either binary or bcd data representation. this bit is not affected by rsmrst# nor any other reset signal. 0 = bcd 1 = binary 1 hour format (hourform) ?r/w. indicates the hour byte format. this bit is not affected by rsmrst# nor any other reset signal. 0 = twelve-hour mode. in twelve hour mode, the seventh bit represents am as zero and pm as one. 1 = twenty-four hour mode. 0 daylight savings enable (dse) ?r/w. triggers two special hour updates per year. the days for the hour adjustment are those specified in united states federal law as of 1987, which is different than previous years. this bit is not affected by rsmrst# nor any other reset signal. 0 = daylight savings time updates do not occur. 1 = a) update on the first sunday in april, where time increments from 1:59:59 am to 3:00:00 am. b) update on the last sunday in october when the time first reaches 1:59:59 am, it is changed to 1:00:00 am. the time must increment normally for at least two update cycles (seconds) previous to these conditions for the time change to occur properly. lpc interface bridge registers (d31:f0) 9-50 82801BA ich2 and 82801BAm ich2-m datasheet 9.6.2.3 rtc_regc?register c (flag register) rtc index: 0ch attribute: ro default value: 00u00000 (u: undefined) size: 8-bit lockable: no power well: rtc writes to register c have no effect. 9.6.2.4 rtc_regd?register d (flag register) rtc index: 0dh attribute: r/w default value: 10uuuuuu (u: undefined) size: 8-bit lockable: no power well: rtc bit description 7 interrupt request flag (irqf) ?ro. irqf = (pf * pie) + (af * aie) + (uf *ufe). this also causes the ch_irq_b signal to be asserted. this bit is cleared upon rsmrst# or a read of register c. 6 periodic interrupt flag (pf) ?ro. this bit is cleared upon rsmrst# or a read of register c. 0 = if no taps are specified via the rs bits in register a, this flag will not be set. 1 = periodic interrupt flag will be 1 when the tap specified by the rs bits of register a is 1. 5 alarm flag (af) ?ro. 0 = this bit is cleared upon rtcrst# or a read of register c. 1 = alarm flag will be set after all alarm values match the current time. 4 update-ended flag (uf) ?ro. 0 = the bit is cleared upon rsmrst# or a read of register c. 1 = set immediately following an update cycle for each second. 3:0 reserved. will always report 0. bit description 7 valid ram and time bit (vrt) ?r/w. 0 = this bit should always be written as a 0 for write cycle; however, it will return a 1 for read cycles. 1 = the valid ram and time bit is set to 1 when the pwrgd (power good) signal provided is high. this feature is not typically used. 6 reserved. this bit always returns a 0 and should be set to 0 for write cycles. 5:0 date alarm ?r/w. these bits store the date of month alarm value. if set to 000000b, then a don?t care state is assumed. the host must configure the date alarm for these bits to do anything, yet they can be written at any time. if the date alarm is not enabled, these bits will return zeros to mimic the functionality of the motorola* 146818b. these bits are not affected by reset. 82801BA ich2 and 82801BAm ich2-m datasheet 9-51 lpc interface bridge registers (d31:f0) 9.7 processor interface registers 9.7.1 nmi_sc?nmi status and control register i/o address: 61h attribute: r/w (some bits ro) default value: 00h size: 8-bit lockable: no power well: core bit description 7 serr# nmi source status (serr#_nmi_sts) ?ro. 1 = pci agent detected a system error and pulses the pci serr# line. this interrupt source is enabled by setting bit 2 to 0. to reset the interrupt, set bit 2 to 1 and then set it to 0. when writing to port 61h, this bit must be 0. 6 iochk# nmi source status (iochk_nmi_sts) ?ro. 1 = an isa agent (via serirq) asserted iochk# on the isa bus. this interrupt source is enabled by setting bit 3 to 0. to reset the interrupt, set bit 3 to 0 and then set it to 1. when writing to port 61h, this bit must be a 0. 5 timer counter 2 out status (tmr2_out_sts) ?ro. this bit reflects the current state of the 8254 counter 2 output. counter 2 must be programmed following any pci reset for this bit to have a determinate value. when writing to port 61h, this bit must be a 0. 4 refresh cycle toggle (ref_toggle) ?ro. this signal toggles from either 0 to 1 or 1 to 0 at a rate that is equivalent to when refresh cycles would occur. when writing to port 61h, this bit must be a 0. 3 iochk# nmi enable (iochk_nmi_en) ?r/w. 0 = enabled. 1 = disabled and cleared. 2 pci serr# enable (pci_serr_en) ?r/w. 0 = serr# nmis are enabled. 1 = serr# nmis are disabled and cleared. 1 speaker data enable (spkr_dat_en) ?r/w. 0 = spkr output is a 0. 1 = spkr output is equivalent to the counter 2 out signal value. 0 timer counter 2 enable (tim_cnt2_en) ?r/w. 0 = disable. 1 = enable lpc interface bridge registers (d31:f0) 9-52 82801BA ich2 and 82801BAm ich2-m datasheet 9.7.2 nmi_en?nmi enable (and real time clock index) i/o address: 70h attribute: r/w (special) default value: 80h size: 8-bit lockable: no power well: core note: the rtc index field is write-only for normal operation. this field can only be read in alt-access mode. note, however, that this register is aliased to port 74h (documented in table 19-2), and all bits are readable at that address. 9.7.3 port92?fast a20 and init register i/o address: 92h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 9.7.4 coproc_err?coprocessor error register i/o address: f0h attribute: wo default value: 00h size: 8-bits lockable: no power well: core bits description 7 nmi enable (nmi_en) ?r/w. 0 = enable nmi sources. 1 = disable all nmi sources. 6:0 real time clock index address (rtc_indx) ?r/w. this data goes to the rtc to select which register or cmos ram address is being accessed. bit description 7:2 reserved. 1 alternate a20 gate (alt_a20_gate) ?r/w. this bit is ored with the a20gate input signal to generate a20m# to the processor. 0 = a20m# signal can potentially go active. 1 = this bit is set when init# goes active. 0 interrupt now (init_now )?r/w. when this bit transitions from a 0 to a 1, the ich2 will force init# active for 16 pci clocks. bits description 7:0 coprocessor error (coproc_err) ?wo. any value written to this register will cause ignne# to go active, if ferr# had generated an internal irq13. for ferr# to generate an internal irq13, the coproc_err_en bit (device 31:function 0, offset d0, bit 13) must be 1. 82801BA ich2 and 82801BAm ich2-m datasheet 9-53 lpc interface bridge registers (d31:f0) 9.7.5 rst_cnt?reset control register i/o address: cf9h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core bit description 7:4 reserved. 3 full reset (full_rst) ?r/w. this bit is used to determine the states of slp_s3# and slp_s5# after a cf9 hard reset (sys_rst =1 and rst_cpu is set to 1), after pwrok going low (with rsmrst# high), or after two tco time-outs. 1 = ich2 will drive slp_s3# and slp_s5# low for 3?5 seconds. 0 = ich2 will keep slp_s3# and slp_s5# high. 2 reset processor (rst_cpu) ?r/w. when this bit transitions from a 0 to a 1, it initiates a hard or soft reset, as determined by the sys_rst bit (bit 1 of this register). 1 system reset (sys_rst) ?r/w. this bit is used to determine a hard or soft reset to the processor. 1 = when rst_cpu bit goes from 0 to 1, the ich2 performs a hard reset by activating pcirst# for 1 millisecond. it also resets the resume well bits (except for those noted throughout the datasheet). 0 = when rst_cpu bit goes from 0 to 1, the ich2 performs a soft reset by activating init# for 16 pci clocks. 0 reserved. lpc interface bridge registers (d31:f0) 9-54 82801BA ich2 and 82801BAm ich2-m datasheet 9.8 power management registers (d31:f0) the power management registers are distributed within the pci device 31: function 0 space, as well as a separate i/o range. each register is described below. unless otherwise indicate, bits are in the main (core) power well. bits not explicitly defined in each register are assumed to be reserved. when writing to a reserved bit, the value should always be 0. software should not attempt to use the value read from a reserved bit, as it may not be consistently 1 or 0. 9.8.1 power management pci configuration registers (d31:f0) table 9-8 shows a small part of the configuration space for pci device 31: function 0. it includes only those registers dedicated for power management. some of the registers are only used for legacy power management schemes. 9.8.1.1 gen_pmcon_1?general pm configuration 1 register (pm?d31:f0) offset address: a0h attribute: r/w default value: 00h size: 16-bit lockable: no usage: acpi, legacy power well: core table 9-8. pci configuration map (pm?d31:f0) offset mnemonic register name/function default type 40h?43h acpi_base acpi base address 00000001h r/w 44h acpi_cntl acpi control 00h r/w a0h gen_pmcon_1 general power management configuration 1 0000h r/w a2h gen_pmcon_2 general power management configuration 2 0000h r/w a4h gen_pmcon_3 general power management configuration 3 00h r/w b8?bbh gpi_rout gpi route control 00000000h r/w c0 trp_fwd_en i/o monitor trap forwarding enable c4?cah mon[ n ]_trp_rng i/o monitor[4:7] trap range 0000h r/w cch mon_trp_msk i/o monitor trap range mask 0000h r/w bit description 15:12 ich2 (82801BA): reserved ich2-m (82801BAm): global standby timer timeout count (gst_timeout) ? r/w. for the ich2-m, this field sets the number of clock ticks that the global standby timer counts before generating a wake event. the gst starts counting when the ich2-m enters the s1 state. if a value of 0h is entered in this field, the gst does not count and no wake event is generated. the gst_tick bit sets the tick rate. 11 ich2 (82801BA): reserved ich2-m (82801BAm): global standby timer tick rate (gst_tick) ? r/w. 0 = 1 minute resolution. this yields a gst timeout range of 1 to 15 minutes. 1 = 32 minute resolution, this yields a gst timeout range of 32 minutes to 8 hours. 82801BA ich2 and 82801BAm ich2-m datasheet 9-55 lpc interface bridge registers (d31:f0) 10 software smi rate select (swsmi_rate_sel) ? r/w. 0 = swsmi timer will time out in 64 ms 4 ms (default). 1 = swsmi timer will time out in 1.5 ms 0.5 ms. 9 pwrbtn# level (pwrbtn_lvl )?ro. this read-only bit indicates the current state of the pwrbtn# signal. 0 = low. 1 = high. 8:7 reserved. 6 iia64 processor mode enable (a64_en) ?r/w. set by software to indicate the presence of an ia64 processor. 0 = ia32 processor mode. 1 = ia64 processor mode. 5 cpu slp# enable (cpuslp_en) ?r/w. 0 = disable. . 4 reserved. 3 ich2 (82801BA): reserved ich2-m (82801BAm): intel ? speedstep ? enable (ss_en) ? r/w. 0 = intel ? speedstep ? logic is disabled and the ss_cnt register will not be visible (reads to ss_cnt return 00h and writes have no effect). 1 = intel ? speedstep ? logic is enabled. 2 ich2 (82801BA): reserved ich2-m (82801BAm): pci clkrun# enable (clkrun_en) ? r/w. 0 = disable. ich2-m drives the clkrun# signal low. 1 = enable clkrun# logic to control the system pci clock via the clkrun# and stp_pci# signals. note that when the slp_en# bit is set, the ich2-m drives the clkrun# signal low, regardless of the state of the clkrun_en bit. this ensures that the pci and lpc clocks continue running during a transition to a sleep state. 1:0 periodic smi# rate select (per_smi_sel) ?r/w. set by software to control the rate at which periodic smi# is generated. 00 = 1 minute 01 = 32 seconds 10 = 16 seconds 11 = 8 seconds bit description ich2 (82801BA): 1 = enables the cpuslp# signal to go active in the s1 state. this reduces the processor power. note that cpuslp# will go active on entry to s3, s4 and s5 even if this bit is not set. ich2-m (82801BAm): 1 = enables the cpuslp# signal to go active in the c3 state. this reduces the processor power. note that cpuslp# goes active during speedstep? transitions and on entry to s1, s3, s4 and s5 even if this bit is not set. lpc interface bridge registers (d31:f0) 9-56 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.1.2 gen_pmcon_2?general pm configuration 2 register (pm?d31:f0) offset address: a2h attribute: r/wc default value: 00h size: 16-bit lockable: no usage: acpi, legacy power well: resume bit description 7:2 reserved. 1 cpu power failure (cpupwr_flr) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. . 0 pwrok failure (pwrok_flr) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position, or when the system goes into a g3 state. 1 = this bit will be set any time pwrok goes low, when the system was in s0 or s1 state. the bit will be cleared only by software by writing a 1 to this bit or when the system goes to a g3 state. note: traditional designs have a reset button logically anded with the pwrok signal from the power supply and the processor?s voltage regulator module. if this is done with the ich2, the pwrok_flr bit will be set. the ich2 treats this internally as if the rsmrst# signal had gone active. however, it is not treated as a full power failure. if pwrok goes inactive and then active (but rsmrst# stays high), then the ich2 will reboot (regardless of the state of the afterg3 bit). if the rsmrst# signal also goes low before pwrok goes high, then this is a full power failure and the reboot policy is controlled by the afterg3 bit. ich2 (82801BA): 1 = indicates that the vrmpwrgd signal from the processor?s vrm went low. ich2-m (82801BAm): 1 = indicates that the vgate signal from the processor?s vrm went low. this bit will not be set if vgate went low due to a intel ? speedstep ? transition. 82801BA ich2 and 82801BAm ich2-m datasheet 9-57 lpc interface bridge registers (d31:f0) 9.8.1.3 gen_pmcon_3?general pm configuration 3 register (pm?d31:f0) offset address: a4h attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: rtc 9.8.1.4 gpi_rout?gpi routing control register (pm?d31:f0) offset address: b8h?bbh attribute: r/w default value: 0000h size: 32-bit lockable: no power well: resume note: gpios that are not implemented will not have the corresponding bits implemented in this register. bit description 7:3 reserved. 2 rtc power status (rtc_pwr_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = indicates that the rtc battery was removed or failed. this bit is set when rtcrst# signal is low. note: clearing cmos in an ich-based platform can be done by using a jumper on rtcrst# or gpi, or using safemode strap. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. 1 power failure (pwr_flr) ?r/wc. this bit is in the rtc well and is not cleared by any type of reset except rtcrst#. 0 = indicates that the trickle current has not failed since the last time the bit was cleared. software clears this bit by writing a 1 to the bit position. 1 = indicates that the trickle current (from the main battery or trickle supply) was removed or failed. note: clearing cmos in an ich-based platform can be done by using a jumper on rtcrst# or gpi, or using safemode strap. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. 0 after g3 state select (afterg3_en) ?r/w. determines what state to go to when power is re- applied after a power failure (g3 state). this bit is in the rtc well and is not cleared by any type of reset except writes to cf9h or rtcrst#. 0 = system will return to s0 state (boot) after power is re-applied. 1 = system will return to the s5 state (except if it was in s4, in which case it will return to s4). in the s5 state, the only enabled wake event is the power button or any enabled wake event that was preserved through the power failure. bit description 31:30 gpi[15] route ?r/w. see bits 1:0 for description. same pattern for gpi[14] through gpi[3] 5:4 gpi[2] route ?r/w. see bits 1:0 for description. 3:2 gpi[1] route ?r/w. see bits 1:0 for description. 1:0 gpi[0] route ?r/w. gpio[13:11,8:6,4:3,1:0] can be routed to cause an smi or sci when the gpi[n]_sts bit is set. if the gpio is not set to an input, this field has no effect. if the system is in an s1?s5 state and if the gpe1_en bit is also set, then the gpi can cause a wake event, even if the gpi is not routed to cause an smi# or sci. 00 = no effect. 01 = smi# (if corresponding gpe1_en bit is also set) 10 = sci (if corresponding gpe1_en bit is also set) 11 = reserved lpc interface bridge registers (d31:f0) 9-58 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.1.5 trp_fwd_en?io monitor trap forwarding enable register (pm?d31:f0) offset address: c0h attribute: r/w (special) default value: 00h size: 8 bits lockable: no usage: legacy only power well: core the ich2 uses this register to enable the monitors to forward cycles to lpc, independent of the pos_dec_en bit and the bits that enable the monitor to generate an smi#. the only criteria is that the address passes the decoding logic as determined by the mon[ n ]_trp_rng and mon_trp_msk register settings. bit description 7 monitor 7 forward enable (mon7_fwd_en )?r/w. 0 = disable. cycles trapped by i/o monitor 7 will not be forwarded to lpc. 1 = enable. cycles trapped by i/o monitor 7 will be forwarded to lpc. 6 monitor 6 forward enable (mon6_fwd_en )?r/w. 0 = disable. cycles trapped by i/o monitor 6 will not be forwarded to lpc. 1 = enable. cycles trapped by i/o monitor 6 will be forwarded to lpc. 5 monitor 5 forward enable (mon5_fwd_en )?r/w. 0 = disable. cycles trapped by i/o monitor 5 will not be forwarded to lpc. 1 = enable. cycles trapped by i/o monitor 5 will be forwarded to lpc. 4 monitor 4 forward enable (mon4_fwd_en )?r/w. 0 = disable. cycles trapped by i/o monitor 4 will not be forwarded to lpc. 1 = enable. cycles trapped by i/o monitor 4 will be forwarded to lpc. 3:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 9-59 lpc interface bridge registers (d31:f0) 9.8.1.6 mon[ n ]_trp_rng?i/o monitor [4:7] trap range register for devices 4?7 (pm?d31:f0) offset address: c4h, c6h, c8h, cah attribute: r/w default value: 00h size: 16 bits lockable: no usage: legacy only power well: core these registers set the ranges that device monitors 4?7 should trap. offset 4ch corresponds to monitor 4. offset c6h corresponds to monitor 5, etc. if the trap is enabled in the mon_smi register and the address is in the trap range (and passes the mask set in the mon_trp_msk register) the ich2 generates an smi#. this smi# occurs if the address is positively decoded by another device on pci or by the ich2 (because it would be forwarded to lpc or some other ich2 internal registers). the trap ranges should not point to registers in the ich2?s internal ide, usb, ac?97 or lan i/o space. if the cycle is to be claimed by the ich2 and targets one of the permitted ich2 internal registers (interrupt controller, rtc, etc.), the cycle will complete to the intended target and an smi# will be generated (this is the same functionality as the ich component). if the cycle is to be claimed by the ich2 and the intended target is on lpc, an smi# will be generated but the cycle will only be forwarded to the intended target if forwarding to lpc is enabled via the trp_fwd_en register settings. 9.8.1.7 mon_trp_msk?i/o monitor trap range mask register for devices 4?7 (pm?d31:f0) offset address: cch attribute: r/w default value: 00h size: 16 bits lockable: no usage: legacy only power well: core bit description 15:0 monitor trap base address (mon[ n ]_trap_base) ?r/w. base i/o locations that mon[ n ] traps (where n = 4, 5, 6 or 7). the range can be mapped anywhere in the processor i/o space (0?64 kb). any access to the range will generate an smi# if enabled by the associated dev[ n ]_trap_en bit in the mon_smi register (pmbase +40h). bit description 15:12 monitor 7 forward mask (mon7_mask) ?r/w. selects low 4-bit mask for the i/o locations that mon7 will trap. similar to mon4_mask. 11:8 monitor 6 forward mask (mon6_mask )?r/w. selects low 4-bit mask for the i/o locations that mon6 will trap. similar to mon4_mask. 7:4 monitor 5 forward mask (mon5_mask) ?r/w. selects low 4-bit mask for the i/o locations that mon5 will trap. similar to mon4_mask. 3:0 monitor 4 forward mask (mon4_mask) ?r/w. selects low 4-bit mask for the i/o locations that mon7 will trap. when a mask bit is set to a 1, the corresponding bit in the base i/o selection will not be decoded. for example, if mon4_trap_base = 1230h, and mon4_msk = 0011b, the ich2 will decode 1230h, 1231h, 1232h, and 1233h for monitor 4. lpc interface bridge registers (d31:f0) 9-60 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.2 apm i/o decode table 9-9 shows the i/o registers associated with apm support. this register space is enabled in the pci device 31: function 0 space (apmdec_en), and cannot be moved (fixed i/o location). 9.8.2.1 apm_cnt?advanced power management control port register i/o address: b2h attribute: r/w default value: 00h size: 8-bit lockable: no usage: legacy only power well: core 9.8.2.2 apm_sts?advanced power management status port register i/o address: b3h attribute: r/w default value: 00h size: 8-bit lockable: no usage: legacy only power well: core table 9-9. apm register map address mnemonic register name/function default type b2h apm_cnt advanced power management control port 00h r/w b3h apm_sts advanced power management status port 00h r/w bit description 7:0 used to pass an apm command between the os and the smi handler. writes to this port not only store data in the apmc register but also generate an smi# when the apmc_en bit is set. bit description 7:0 used to pass data between the os and the smi handler. basically, this is a scratchpad register and is not effected by any other register or function (other than a pci reset). 82801BA ich2 and 82801BAm ich2-m datasheet 9-61 lpc interface bridge registers (d31:f0) 9.8.3 power management i/o registers table 9-10 shows the registers associated with acpi and legacy power management support. these registers are enabled in the pci device 31: function 0 space (pm_io_en), and can be moved to any i/o location (128-byte aligned). the registers are defined to be compliant with the acpi 1.0 specification, and use the same bit names. note: all reserved bits and registers will always return 0 when read, and will have no effect when written. table 9-10. acpi and legacy i/o register map pmbase+ offset register name acpi pointer default attributes 00?01h pm1 status pm1a_evt_blk 0000h r/w 02?03h pm1 enable pm1a_evt_blk+2 0000h r/w 04?07h pm1 control pm1a_cnt_blk 00000000h r/w 08?0bh pm1 timer pmtmr_blk 00000000h ro 0ch reserved ? ? ? 10h?13h processor control p_blk 00000000h r/w 14h level 2 p_blk+4 00h ro 15h ich2 (82801BA): reserved ich2-m (82801BAm): level 3 ? p_blk+5 ? 0000h ? ro 16?19h reserved ? ? ? 20h ich2 (82801BA): reserved ich2-m (82801BAm): pm2 control ? pm2a_cnt_blk ? 0000h ? r/w 28?29h general purpose event 0 status gpe0_blk 0000h r/w 2a?2bh general purpose event 0 enables gpe0_blk+2 0000h r/w 2c?2d general purpose event 1 status gpe1_blk 0000h r/w 2e?2f general purpose event 1 enables gpe1_blk+2 0000h r/w 30?31h smi# control and enable ? 0000h r/w 34?35h smi status register ? 0000h r/w 36?3fh reserved ? 0000h ro 40h monitor smi status ? 0000h r/w 42h reserved ? ? ? 44h device trap status ? 0000h r/w 48h trap enable register ? 0000h r/w 4ch?4dh bus address tracker ? last cycle ro 4eh bus cycle tracker ? last cycle ro 50h ich2 (82801BA): reserved ich2-m (82801BAm): speedstep? control ? ? ? 00h ? wo 51?5fh reserved ? ? ? 60h?7fh reserved for tco registers ? ? ? lpc interface bridge registers (d31:f0) 9-62 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.1 pm1_sts?power management 1 status register i/o address: pmbase + 00h ( acpi pm1a_evt_blk) attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: bits 0?7: core, bits 8?15: resume, except bit 11 in rtc if bit 10 or 8 in this register is 1 and the corresponding _en bit is set in the pm1_en register, ich2 generates a wake event. once back in an s0 state (or if already in s0 state when the event occurs), ich2 also generates an sci if the sci_en bit is set or an smi# if the sci_en bit is not set. note: bit 5 does not cause an smi# or a wake event. bit 0 does not cause a wake event but can cause an smi# or sci. bit description 15 wake status (wak_sts) ?r/wc. this bit is not affected by hard resets caused by a cf9 write but is reset by rsmrst#. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the system is in one of the sleep states (via the slp_en bit) and an enabled wake event occurs. upon setting this bit, the ich2 will transition the system to the on state. if the afterg3_en bit is not set and a power failure occurs without the slp_en bit set, the system will return to an s0 state when power returns, and the wak_sts bit will not be set. for the 82801BAm ich2-m, power failure could result from removing the batteries. if the afterg3_en bit is set and a power failure occurs without the slp_en bit having been set, the system will go into an s5 state when power returns and a subsequent wake event will cause the wak_sts bit to be set. note that any subsequent wake event would have to be caused by either a power button press or an enabled wake event that was preserved through the power failure (enable bit in the rtc well). 14:12 reserved 11 power button override status (prbtnor_sts) ?r/wc. this bit is not affected by hard resets caused by a cf9 write and is not reset by rsmrst#. thus, this bit will be preserved through a power failure. 0 = the bios or sci handler can clear this bit by writing a 1 to it. 1 = set by hardware anytime a power button override event occurs which occurs when the power button is pressed for at least 4 consecutive seconds. the power button override causes an unconditional transition to the s5 state and sets the afterg3 bit. this bit can also be set by the smbus slave logic. 10 rtc status (rtc_sts) ?r/wc. this bit is not affected by hard resets caused by a cf9 write but is reset by rsmrst#. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the rtc generates an alarm (assertion of the irq8# signal). additionally if the rtc_en bit is set, the setting of the rtc_sts bit will generate a wake event. 9 reserved 8 power button status (pwrbtn_sts) ?r/wc. this bit is not affected by hard resets caused by a cf9 write. 1 = this bit is set by hardware when the pwrbtn# signal is asserted low, independent of any other enable bit. in the s0 state, while pwrbtn_en and pwrbtn_sts are both set, an sci (or smi# if sci_en is not set) will be generated. in any sleeping state s1?s5, while pwrbtn_en and pwrbtn_sts are both set, a wake event is generated. 0 = if the pwrbtn# signal is held low for more than 4 seconds, the hardware clears the pwrbtn_sts bit, sets the pwrbtnor_sts bit, and the system transitions to the s5 state with only pwrbtn# enabled as a wake event. this bit can be cleared by software by writing a one to the bit position. 82801BA ich2 and 82801BAm ich2-m datasheet 9-63 lpc interface bridge registers (d31:f0) 7:6 reserved 5 global status (gbl _sts) ?r/wc. 1 = set when an sci is generated due to bios wanting the attention of the sci handler. bios has a corresponding bit, bios_rls, which will cause an sci and set this bit. 0 = the sci handler should then clear this bit by writing a 1 to the bit location. 4 ich2 (82801BA): reserved ich2-m (82801BAm): bus master status (bm_sts) ? r/wc. 1 = set by the ich2-m when a bus master requests a break from the c3 state (the bus master break events are generated by pirq[x]# assertion or bus master activity by any of ich2-m?s internal bus masters). bus master activity is detected by any of the pci requests being active, any internal bus master request being active, the agpbusy# signal being active, or activity on either of the ich2-m?s usb controllers. a usb controller is considered active if all three of the following conditions are true 1. the controller is not in global suspend 2. at least one of the controller?s ports is not suspended 3. the usb run bit is set bus master ide controller activity also causes bm_sts to be set. the ich2-m?s bmide controller is considered active when the controller?s start bit is set. 0 = software clears this bit by writing a 1 to the bit position. 3:1 reserved 0 timer overflow status (tmrof_sts) ?r/wc. 1 = this bit gets set any time bit 22 of the 24-bit timer goes high (bits are numbered from 0 to 23). this will occur every 2.3435 seconds. when the tmrof_en bit is set, then the setting of the tmrof_sts bit will additionally generate an sci or smi# (depending on the sci_en). 0 = the sci or smi# handler clears this bit by writing a 1 to the bit location. bit description lpc interface bridge registers (d31:f0) 9-64 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.2 pm1_en?power management 1 enable register i/o address: pmbase + 02h ( acpi pm1a_evt_blk + 2) attribute: r/w default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: bits 0?7: core, bits 8?15: resume bit description 15:11 reserved. 10 rtc event enable (rtc_en) ?r/w. this bit is in the rtc well to allow an rtc event to wake after a power failure. this bit is not cleared by any reset other than rtcrst# or a power button override event. 1 = an sci (or smi#) or wake event will occur when this bit is set and the rtc_sts bit goes active. 0 = no sci (or smi#) or wake event is generated then rtc_sts goes active. 8 power button enable (pwrbtn_en) ?r/w. this bit is used to enable the setting of the pwrbtn_sts bit to generate a power management event (smi#, sci). pwrbtn_en has no effect on the pwrbtn_sts bit being set by the assertion of the power button. the power button is always enabled as a wake event. 0 = disable. 1 = enable. 5 global enable (gbl_en) ?r/w. when both the gbl_en and the gbl_sts are set, an sci is raised. 0 = disable. 1 = enable sci on gbl_sts going active. 0 timer overflow interrupt enable (tmrof_en) ?r/w. works in conjunction with the sci_en bit as described below: tmrof_en sci_en effect when tmrof_sts is set 0 x no smi# or sci 1 0 smi# 1 1 sci 82801BA ich2 and 82801BAm ich2-m datasheet 9-65 lpc interface bridge registers (d31:f0) 9.8.3.3 pm1_cnt?power management 1 control register i/o address: pmbase + 04h ( acpi pm1a_cnt_blk) attribute: r/w default value: 0000h size: 32-bit lockable: no usage: acpi or legacy power well: bits 0?7: core, bits 8?15: resume bit description 13 sleep enable (slp_en)? wo. setting this bit causes the system to sequence into the sleep state defined by the slp_typ field. 12:10 sleep type (slp_typ) ?r/w. this 3-bit field defines the type of sleep the system should enter when the slp_en bit is set to 1. 000 = on: typically maps to s0 state. . 011 = reserved 100 = reserved 101 = suspend-to-ram. assert slp_s1# and slp_s3#; typically, maps to s3 state. 110 = suspend-to-disk. assert slp_s1#, slp_s3#, and slp_s5# slp_s3# and, slp_s5#; typically, maps to s4 state. 111 = soft off. assert slp_s1#, slp_s3#, and slp_s5# slp_s3#, and slp_s5#; typically, maps to s5 state. 2 global release (gbl_rls) ?wo. 1 = acpi software writes a 1 to this bit to raise an event to the bios. bios software has corresponding enable and status bits to control its ability to receive acpi events. 0 = this bit always reads as 0. 1 ich2 (82801BA): reserved ich2-m (82801BAm): bus master reload (bm_rld) ? r/w. this bit is reset to 0 by pcirst# 0 = bus master requests do not cause a break from the c3 state. 1 = enable bus master requests (internal, external or agpbusy#) to cause a break from the c3 state. 0 sci enable (sci_en) ?r/w. selects the sci interrupt or the smi# interrupt for various events including the bits in the pm1_sts register (bit 10, 8, 0), and bits in gpe0_sts. 0 = these events will generate an smi#. 1 = these events will generate an sci. 001 = ich2 (82801BA): assert stpclk#. puts processor in stop-grant state. optional to assert cpuslp# to put processor in sleep state: typically, maps to s1 state. ich2-m (82801BAm): reserved. 010 = ich2 (82801BA): reserved ich2-m (82801BAm): assert slp_s1#: typically, maps to s1 state. lpc interface bridge registers (d31:f0) 9-66 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.4 pm1_tmr?power management 1 timer register i/o address: pmbase + 08h ( acpi pmtmr_blk) attribute: ro default value: xx000000h size: 32-bit lockable: no usage: acpi power well: core 9.8.3.5 proc_cnt?processor control register i/o address: pmbase + 10h ( acpi p_blk) attribute: r/w default value: 00000000h size: 32-bit lockable: no (bits 7:5 are write once) usage: acpi or legacy power well: core bit description 31:24 reserved 23:0 timer value (tmr_val) ?ro. returns the running count of the pm timer. this counter runs off a 3.579545 mhz clock (14.31818 mhz divided by 4). it is reset to zero during a pci reset and then continues counting as long as the system is in the s0 state. anytime bit 22 of the timer goes high to low (bits referenced from 0 to 23), the tmrof_sts bit is set. the high-to-low transition will occur every 2.3435 seconds. if the tmrof_en bit is set, an sci interrupt is also generated. bit description 31:18 reserved. 17 throttle status (thtl_sts) ?ro. 0 = no clock throttling is occurring (maximum processor performance). 1 = indicates that the clock state machine is in some type of low power state (where the processor is not running at its maximum performance): thermal throttling or hardware throttling. 16:9 reserved 8 force thermal throttling (force_thtl) ?r/w. software can set this bit to force the thermal throttling function. this has the same effect as the thrm# signal being active for 2 seconds. 0 = no forced throttling. 1 = throttling at the duty cycle specified in thrm_dty starts immediately (no 2 second delay), and no smi# is generated. 7:5 thermal duty cycle (thrm_dty). this write-once 3-bit field determines the duty cycle of the throttling when the thermal override condition occurs. the duty cycle indicates the approximate percentage of time the stpclk# signal is asserted while in the throttle mode. the stpclk# throttle period is 1024 pciclks. note that the throttling only occurs if the system is in the c0 state. if in the c2 state, no throttling occurs. there is no enable bit for thermal throttling, because it should not be disabled. once the thrm_dty field is written, any subsequent writes will have no effect until pcirst# goes active. thrm_dty throttle mode pci clocks 000 reserved (default) 512 (will be 50%) 001 87.5% 896 010 75.0% 768 011 62.5% 640 100 50% 512 101 37.5% 384 110 25% 256 111 12.5% 128 82801BA ich2 and 82801BAm ich2-m datasheet 9-67 lpc interface bridge registers (d31:f0) 9.8.3.6 lv2?level 2 register i/o address: pmbase + 14h ( acpi p_blk+4) attribute: ro default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: core 9.8.3.7 lv3?level 3 register (82801BAm ich2-m) 4 throttling enable (thtl_en). when this bit is set and the system is in a c0 state, processor- controlled stpclk# throttling is enabled. the duty cycle is selected in the thtl_dty field. 0 = disable 1 = enable 3:1 throttling duty cycle (thtl_dty). this 3-bit field determines the duty cycle of the throttling when the thtl_en bit is set. the duty cycle indicates the approximate percentage of time the stpclk# signal is asserted (low) while in the throttle mode. the stpclk# throttle period is 1024 pciclks. thtl_dty throttle mode pci clocks 000 reserved (default) 512 (will be 50%) 001 87.5% 896 010 75.0% 768 011 62.5% 640 100 50% 512 101 37.5% 384 110 25% 256 111 12.5% 128 0 reserved bit description bit description 7:0 reads to this register return all zeros; writes have no effect. reads to this register generate a ?enter a level 2 power state? (c2) to the clock control logic. this causes the stpclk# signal to go active, and stay active until a break event occurs. throttling (due either to thtl_en or thrm# override) will be ignored. i/o address: pmbase + 15h ( acpi p_blk + 5) attribute: ro default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: core bit description 7:0 reads to this register return all zeros, writes to this register have no effect. reads to this register generate an ?enter a c3 power state? to the clock control logic. the c3 state persists until a break event occurs. lpc interface bridge registers (d31:f0) 9-68 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.8 pm2_cnt?power management 2 control (82801BAm ich2-m) 9.8.3.9 gpe0_sts?general purpose event 0 status register i/o address: pmbase + 28h ( acpi gpe0_blk) attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: acpi power well: resume note: this register is symmetrical to the general purpose event 0 enable register. if the corresponding seen bit is set, then when the _sts bit get set, ich2 generates a wake event. once back in an s0 state (or if already in an s0 state when the event occurs), ich2 also generates an sci if the sci_en bit is set, or an smi# if the sci_en bit is not set. there will be no sci/smi# or wake event on thrmor_sts since there is no corresponding x_en bit. none of these bits are reset by cf9h write. all are reset by rsmrst#. i/o address: pmbase + 20h ( acpi pm2_blk) attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi power well: core bit description 7:1 reserved. 0 arbiter disable (arb_dis) ? r/w. 0 = enable system arbiter. the arbiter can grant the bus to bus masters (internal devices or external pci devices), other than the processor. 1 = disable system arbiter (default). processor has ownership of the system bus and memory. no bus masters (internal or external) are granted the bus. note that after the arbiter is disabled, the processor must not initiate any down-bound reads to pci devices that may have up-bound posted data, as this will result in system deadlock. bit description 15:12 reserved. 11 pme status (pme_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the pme# signal goes active. additionally, if the pme_en bit is set, and the system is in an s0 state, then the setting of the pme_sts bit will generate an sci or smi# (if sci_en is not set). if the pme_en bit is set, and the system is in an s1?s4 state (or s5 state due to setting slp_typ and slp_en), then the setting of the pme_sts bit will generate a wake event, and an sci will be generated. if the system is in an s5 state due to power button override or a power failure, then pme_sts will not cause a wake event or sci. 10 ich2 (82801BA): reserved ich2-m (82801BAm): batlow_sts ? r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the batlow# signal is asserted. 82801BA ich2 and 82801BAm ich2-m datasheet 9-69 lpc interface bridge registers (d31:f0) 9 ich2 (82801BA): reserved ich2-m (82801BAm): global standby timer status (gst_sts) ? r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware to indicate that the wake event was due to gst timeout. this bit will only be set when the system was in the s1 state. 8 ri_sts ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the ri# input signal goes active. 7 smbus wake status (smb_wak_sts) ?r/wc . smbus wake status?r/wc. the smbus controller can independently cause an smi# or sci; thus, this bit does not need to do so (unlike the other bits in this register). 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware to indicate that the wake event was caused by the ich2?s smbus logic. this bit is set by the wake/smi# command type, even if the system is already awake. the smi handler should then clear this bit. 6 tco sci status (tcosci_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the tco logic causes an sci. 5 ac97 status (ac97_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when the codecs are attempting to wake the system. the ac97_sts bit gets set only from the following two cases: 1. acsdin[1] or acsdin[0] is high and bitclk is not oscillating, or 2. the gsci bit is set (section 13.2.9, nambar +30h, bit 0) 4 usb controller 2 status (usb2_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when usb controller 2 needs to cause a wake. wake event will be generated if the corresponding usb2_en bit is set. 3 usb controller 1 status (usb1_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware when usb controller 1 needs to cause a wake. wake event will be generated if the corresponding usb1_en bit is set. 2 reserved. 1 thermal interrupt override status (thrmor_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = this bit is set by hardware anytime a thermal over-ride condition occurs and starts throttling the processor?s clock at the thrm_dty ratio. this will not cause an smi#, sci, or wake event. 0 thermal interrupt status (thrm_sts) ?r/wc. 0 = software clears this bit by writing a 1 to the bit position. 1 = set by hardware anytime the thrm# signal is driven active as defined by the thrm_pol bit. additionally, if the thrm_en bit is set, then the setting of the thrm_sts bit will also generate a power management event (sci or smi#). bit description lpc interface bridge registers (d31:f0) 9-70 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.10 gpe0_en?general purpose event 0 enables register i/o address: pmbase + 2ah ( acpi gpe0_blk + 2) attribute: r/w default value: 0000h size: 16-bit lockable: no usage: acpi power well: bits 0?7 resume, bits 8?15 rtc note: this register is symmetrical to the general purpose event 0 status register. all the bits in this register should be cleared to 0 based on a power button override. the resume well bits are all cleared by rsmrst#. the rtc sell bits are cleared by rtcrst#. bit description 15:12 reserved. 11 pme# enable (pme_en) ?r/w. 0 = disable. 1 = enables the setting of the pme_sts to generate a wake event and/or an sci. pme# can be a wake event from the s1?s4 state or from s5 (if entered via slp_en, but not power button override). 10 ich2 (82801BA): reserved ich2-m (82801BAm): batlow_en ? r/w. 0 = disable. 1 = enables the batlow# signal to cause an smi# or sci (depending on the sci_en bit) when it goes low. this bit does not prevent the batlow# signal from inhibiting the wake event. 9 reserved 8 ri_en ?r/w. the value of this bit will be maintained through a g3 state and is not affected by a hard reset caused by rsmrst# or a cf9h write. assertion of rtcrst# resets this bit. 0 = disable. 1 = enables the setting of the ri_sts to generate a wake event. 7 reserved 6 tco sci enable (tcosci_en) ?r/w. 0 = disable. 1 = enables the setting of the tcosci_sts to generate an sci. 5 ac97 enable (ac97_en) ?r/w. 0 = disable. 1 = enables the setting of the ac97_sts to generate a wake event. 4 usb controller 2 enable (usb2_en) ?r/w. 0 = disable. 1 = enables the setting of the usb2_sts to generate a wake event. 3 usb controller 1 enable (usb1_en) ?r/w. 0 = disable. 1 = enables the setting of the usb1_sts to generate a wake event. 2 thermal pin polarity (thrm#_pol) ?r/w. this bit controls the polarity of the thrm# pin needed to set the thrm_sts bit. 0 = low value on the thrm# signal will set the thrm_sts bit. 1 = high value on the thrm# signal will set the thrm_sts bit. 1 reserved. 0 thermal signal reporting enable (thrm_en) ?r/w. 0 = disable. 1 = active assertion of the thrm# signal (as defined by the thrm_pol bit) will set the thrm_sts bit and generate a power management event (sci or smi). 82801BA ich2 and 82801BAm ich2-m datasheet 9-71 lpc interface bridge registers (d31:f0) 9.8.3.11 gpe1_sts?general purpose event 1 status register i/o address: pmbase + 2ch ( acpi gpe1_blk) attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: acpi power well: resume note: this register is symmetrical to the general purpose event 1 enable register. gpios that are not implemented will not have the corresponding bits implemented in this register. note: bits 5 and 2 are not implemented since gpio5 and gpio2 are not implemented. bit description 15:6 gpi[15:6] status (gpi[15:6]_sts) ?r/wc. 0 = software clears each bit by writing a 1 to the bit position when the corresponding gpio signal is not active. (the status bit cannot be cleared while the corresponding signal is still active). 1 = these bits are set any time the corresponding gpio is set up as an input and the corresponding gpio signal is low (or high if the corresponding gp_inv bit is set). if the corresponding gpi[n]_en bit is set in the gpe1_en register, and the gpi[n]_sts bit is set, then: - if the system is in an s1_s5 state, the event will also wake the system. - if the system is in an s0 state (or upon waking back to an s0 state), an smi# or sci will be generated, depending on the gpi_rout bits for the corresponding gpi. 5 reserved 4:3 gpi[4:3] status (gpi[4:3]_sts) ?r/wc. 0 = software clears each bit by writing a 1 to the bit position when the corresponding gpio signal is not active. (the status bit cannot be cleared while the corresponding signal is still active). 1 = these bits are set any time the corresponding gpio is set up as an input and the corresponding gpio signal is low (or high if the corresponding gp_inv bit is set). if the corresponding gpi[n]_en bit is set in the gpe1_en register, and the gpi[n]_sts bit is set, then: - if the system is in an s1_s5 state, the event will also wake the system. - if the system is in an s0 state (or upon waking back to an s0 state), an smi# or sci will be generated, depending on the gpi_rout bits for the corresponding gpi. 2 reserved 1:0 gpi[1:0] status (gpi[1:0]_sts) ?r/wc. 0 = software clears each bit by writing a 1 to the bit position when the corresponding gpio signal is not active. (the status bit cannot be cleared while the corresponding signal is still active). 1 = these bits are set any time the corresponding gpio is set up as an input and the corresponding gpio signal is low (or high if the corresponding gp_inv bit is set). if the corresponding gpi[n]_en bit is set in the gpe1_en register, and the gpi[n]_sts bit is set, then: - if the system is in an s1_s5 state, the event will also wake the system. - if the system is in an s0 state (or upon waking back to an s0 state), an smi# or sci will be generated, depending on the gpi_rout bits for the corresponding gpi. lpc interface bridge registers (d31:f0) 9-72 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.12 gpe1_en?general purpose event 1 enable register i/o address: pmbase + 2eh ( acpi gpe1_blk + 2) attribute: r/w default value: 0000h size: 16-bit lockable: no usage: acpi power well: resume note: this register is symmetrical to the general purpose event 1 status register. gpios that are not implemented will not have the corresponding bits implemented in this register. all of the bits in this register will be cleared by rsmrst#. note: bits 5 and 2 are not implemented since gpio5 and gpio2 are not implemented. 9.8.3.13 smi_en?smi control and enable register i/o address: pmbase + 30h attribute: r/w default value: 0000h size: 32 bit lockable: no usage: acpi or legacy power well: core bit description 15:6 gpi[15:6] enable (gpi[15:6]_en) ?r/w. 1 = enable the corresponding gpi[n]_sts bit being set to cause an smi#, sci, and/or wake event. 0 = disable. 5 reserved 4:3 gpi[4:3] enable (gpi[4:3]_en) ?r/w. 1 = enable the corresponding gpi[n]_sts bit being set to cause an smi#, sci, and/or wake event. 0 = disable. 2 reserved 1:0 gpi[1:0] enable (gpi[1:0]_en )?r/w. 1 = enable the corresponding gpi[n]_sts bit being set to cause an smi#, sci, and/or wake event. 0 = disable. bit description 31:15 reserved 14 periodic smi# enable (periodic_en )?r/w. 0 = disable. 1 = enables the ich2 to generate an smi# when the periodic_sts bit is set in the smi_sts register. 13 tco enable (tco_en) ?r/w. 0 = disables tco logic generating an smi#. note that if the nmi2smi_en bit is set, smis that are caused by re-routed nmis will not be gated by the tco_en bit. even if the tco_en bit is 0, nmis will still be routed to cause smis. 1 = enables the tco logic to generate smi#. 12 reserved 11 microcontroller smi# enable (mcsmi_en) ?r/w. 0 = disable. 1 = enables ich2 to trap accesses to the microcontroller range (62h or 66h) and generate an smi#. note that ?trapped? cycles will be claimed by the ich2 on pci, but not forwarded to lpc. 10:8 reserved 82801BA ich2 and 82801BAm ich2-m datasheet 9-73 lpc interface bridge registers (d31:f0) 7 bios release (bios_rls) ?wo. 0 = this bit will always return 0 on reads. writes of 0 to this bit have no effect. 1 = enables the generation of an sci interrupt for acpi software when a one is written to this bit position by bios software. 6 software smi# timer enable (swsmi_tmr_en) ?r/w. 0 = disable. clearing the swsmi_tmr_en bit before the timer expires will reset the timer and the smi# will not be generated. 1 = starts software smi# timer. when the swsmi timer expires (the time-out period depends upon the swsmi_rate_sel bit setting), swsmi_tmr_sts is set and an smi# is generated. swsmi_tmr_en stays set until cleared by software. 5 apmc enable (apmc_en) ?r/w. 0 = disable. writes to the apm_cnt register will not cause an smi#. 1 = enables writes to the apm_cnt register to cause an smi#. 4 slp smi enable (slp_smi_en) ?r/w. 0 = disables the generation of smi# on slp_en. note that this bit must be 0 before the software attempts to transition the system into a sleep state by writing a 1 to the slp_en bit. 1 = a write of 1 to the slp_en bit (bit 13 in pm1_cnt register) will generate an smi#, and the system will not transition to the sleep state based on that write to the slp_en bit. 3 legacy usb enable (legacy_usb_en) ?r/w. 0 = disable. 1 = enables legacy usb circuit to cause smi#. 2 bios enable (bios_en) ?r/w. 0 = disable. 1 = enables the generation of smi# when acpi software writes a 1 to the gbl_rls bit. 1 end of smi (eos) ?r/w (special). this bit controls the arbitration of the smi signal to the processor. this bit must be set for the ich2 to assert smi# low to the processor. 1 = when this bit is set, smi# signal will be deasserted for 4 pci clocks before its assertion. in the smi handler, the processor should clear all pending smis (by servicing them and then clearing their respective status bits), set the eos bit, and exit smm. this will allow the smi arbiter to re- assert smi upon detection of an smi event and the setting of a smi status bit. 0 = once the ich2 asserts smi# low, the eos bit is automatically cleared. 0 global smi enable (gbl_smi_en) ?r/w. 0 = no smi# will be generated by ich2. this bit is reset by a pci reset event. 1 = enables the generation of smi# in the system upon any enabled smi event. bit description lpc interface bridge registers (d31:f0) 9-74 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.14 smi_sts?smi status register i/o address: pmbase + 34h attribute: r/w default value: 0000h size: 32-bit lockable: no usage: acpi or legacy power well: core note: if the corresponding _en bit is set when the _sts bit is set, the ich2 will cause an smi# (except bits 8:10 and 12, which do not need enable bits since they are logic ors of other registers that have enable bits). bit description 31:17 reserved 16 smbus smi status (smbus_smi_sts) ?r/wc. 1 = indicates that the smi# was caused by either the smbus slave receiving a message, or the smbalert# signal going active. this bit will be set on smbalert# assertion only if the smbus host controller is programmed to generate smis (not interrupts). 0 = this bit is cleared by writing a 1 to its bit position. 15 serr irq smi status (serirq_smi_sts) ?ro. 1 = indicates that the smi# was caused by the serirq decoder. 0 = smi# was not caused by serirq decoder. this is not a sticky bit. 14 periodic status (periodic_sts) ?r/wc. 1 = this bit will be set at the rate determined by the per_smi_sel bits. if the periodic_en bit is also set, the ich2 will generate an smi#. 0 = this bit is cleared by writing a 1 to its bit position. 13 tco status (tco_sts) ?ro. 0 = smi# not caused by tco logic. 1 = indicates the smi# was caused by the tco logic. note that this is not a wake event. 12 device monitor status (devmon_sts) ?ro. 1 = set under any of the following conditions: - any of the dev[7:4]_trap_sts bits are set and the corresponding dev[7:4]_trap_en bits are also set. - any of the devtrap_sts bits are set and the corresponding devtrap_en bits are also set. 0 = smi# not caused by device monitor. 11 microcontroller smi# status (mcsmi_sts) ?r/wc. 0 = indicates that there has been no access to the power management microcontroller range (62h or 66h). this bit is cleared by software writing a 1 to the bit position. 1 = set if there has been an access to the power management microcontroller range (62h or 66h). if this bit is set, and the mcsmi_en bit is also set, the ich2 will generate an smi#. 10 gpe1 status (gpe1_sts )?ro. this bit is a logical or of the bits in the gpe1_sts register that are also set up to cause an smi# (as indicated by the gpi_rout registers) and have the corresponding bit set in the gpe1_en register. bits that are not routed to cause an smi# will have no effect on the gpe1_sts bit. 0 = smi# was not generated by a gpi assertion. 1 = smi# was generated by a gpi assertion. 9 gpe0 status (gpe0_sts) ?ro. this bit is a logical or of the bits in the gpe0_sts register that also have the corresponding bit set in the gpe0_en register. 0 = smi# was not generated by a gpe0 event. 1 = smi# was generated by a gpe0 event. 8 pm1 status register (pm1_sts_reg) ?ro. this is an or of the bits in the acpi pm1 status register (offset pmbase+00h) that can cause an smi#. 0 = smi# was not generated by a pm1_sts event. 1 = smi# was generated by a pm1_sts event. 7 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 9-75 lpc interface bridge registers (d31:f0) 9.8.3.15 mon_smi?device monitor smi status and enable register i/o address: pmbase +40h attribute: r/w, r/wc default value: 0000h size: 16-bit lockable: no usage: legacy only power well: core 6 software smi timer status (swsmi_tmr_sts) ?r/wc. 1 = set by the hardware when the software smi# timer expires. 0 = software clears this bit by writing a 1 to the bit location. 5 apm status (apm_sts) ?r/wc. 1 = smi# was generated by a write access to the apm control register with the apmc_en bit set. 0 = software clears this bit by writing a 1 to the bit location. 4 slp smi status (slp_smi_sts) ?r/wc. 1 = indicates an smi# was caused by a write of 1 to slp_en bit when slp_smi_en bit is also set. 0 = software clears this bit by writing a 1 to the bit location. 3 legacy usb status (legacy_usb_sts )?ro. this bit is a logical or of each of the smi status bits in the usb legacy keyboard/mouse control registers anded with the corresponding enable bits. this bit will not be active if the enable bits are not set. 0 = smi# was not generated by usb legacy event. 1 = smi# was generated by usb legacy event. 2 bios status (bios_sts) ?r/wc. 1 = smi# was generated due to acpi software requesting attention (writing a 1 to the gbl_rls bit with the bios_en bit set). 0 = this bit cleared by software writing a 1 to its bit position. 1:0 reserved. bit description bit description 15:12 device 7:4 trap status (dev[7:4]_trap_sts) ?r/wc. bit 12 corresponds to monitor 4, bit 13 corresponds to monitor 5 etc. 1 = smi# was caused by an access to the corresponding device monitor?s i/o range. 0 = smi# was not caused by the associated device monitor. 11:8 device 7:4 trap enable (dev[7:4]_trap_en) ?r/w. bit 8 corresponds to monitor 4, bit 9 corresponds to monitor 5 etc. 1 = enables smi# due to an access to the corresponding device monitor?s i/o range. 0 = disable. 7:0 reserved lpc interface bridge registers (d31:f0) 9-76 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.16 devact_sts?device activity status register i/o address: pmbase +44h attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: legacy only power well: core this register is used in conjunction with the periodic smi# timer to detect any system activity for legacy power management. bit description 15:14 reserved 13 adlib activity status (adlib_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 12 keyboard controller activity status (kbc_act_sts) ?r/wc. kbc (60/64h). 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 11 midi activity status (midi_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 10 audio activity status (audio_act_sts) ?r/wc. audio (sound blaster ?ored? with mss). 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 9 pirq[d or h] activity status (pirqdh_act_sts) ?r/wc. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci interrupts has been active. clear this bit by writing a 1 to the bit location. 8 pirq[c or g] activity status (pirqcg_act_sts) ?r/wc. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci interrupts has been active. clear this bit by writing a 1 to the bit location. 7 pirq[b or f] activity status (pirqbf_act_sts) ?r/wc. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci interrupts has been active. clear this bit by writing a 1 to the bit location. 6 pirq[a or e] activity status (pirqae_act_sts) ?r/wc. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci interrupts has been active. clear this bit by writing a 1 to the bit location. 5 legacy activity status (leg_act_sts) ?r/wc. parallel port, serial port 1, serial port 2, floppy disk controller. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 4 reserved. 3 ide secondary drive 1 activity status (ides1_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 2 ide secondary drive 0 activity status (ides0_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 82801BA ich2 and 82801BAm ich2-m datasheet 9-77 lpc interface bridge registers (d31:f0) 9.8.3.17 devtrap_en?device trap enable register i/o address: pmbase +48h attribute: r/w default value 0000h size: 16-bit lockable: no usage: legacy only power well: core this register enables the individual trap ranges to generate an smi# when the corresponding status bit in the devact_sts register is set. when a range is enabled, i/o cycles associated with that range will not be forwarded to lpc or ide. 1 ide primary drive 1 activity status (idep1_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. 0 ide primary drive 0 activity status (idep0_act_sts) ?r/wc. 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed. clear this bit by writing a 1 to the bit location. bit description bit description 15:14 reserved 13 adlib trap enable (adlib_trp_en) ?r/w. 0 = disable. 1 = enable. 12 kbc trap enable (kbc_trp_en) ?r/w. kbc (60/64h). 0 = disable. 1 = enable. 11 midi trap enable (midi_trp_en) ?r/w. 0 = disable. 1 = enable. 10 audio trap enable (audio_trp_en) ?r/w. audio (sound blaster ?ored? with mss). 0 = disable. 1 = enable. 9:6 reserved 5 leg_io_trp_en ?r/w. parallel port, serial port 1, serial port 2, floppy disk controller. 0 = disable. 1 = enable. 4 reserved. 3 ide secondary drive 1 trap enable (ides1_trp_en) ?r/w. 0 = disable. 1 = enable. 2 ide secondary drive 0 trap enable (ides0_trp_en)? r/w. 0 = disable. 1 = enable. 1 ide primary drive 1 trap enable (idep1_trp_en) ?r/w. 0 = disable. 1 = enable. 0 ide primary drive 0 trap enable (idep0_trp_en)? r/w. 0 = disable. 1 = enable. lpc interface bridge registers (d31:f0) 9-78 82801BA ich2 and 82801BAm ich2-m datasheet 9.8.3.18 bus_addr_track?bus address tracker register i/o address: pmbase +4ch attribute: ro lockable: no size: 16-bit power well: core usage: legacy only this register could be used by the smi# handler to assist in determining what was the last cycle from the processor. 9.8.3.19 bus_cyc_track?bus cycle tracker register i/o address: pmbase +4eh attribute: ro lockable: no size: 8-bit power well: core usage: legacy only this register could be used by the smm handler to assist in determining what was the last cycle from the processor. 9.8.3.20 ss_cnt? speedstep ? control register (82801BAm ich2-m) bit description 15:0 corresponds to the low 16 bits of the last i/o cycle, as would be defined by the pci ad[15:0] signals on the pci bus (even though it may not be a real pci cycle). the value is latched based on smi# active. this functionality is useful for figuring out which i/o was last being accessed. bit description 7:4 corresponds to the byte enables, as would be defined by the pci c/be# signals on the pci bus (even though it may not be a real pci cycle). the value is latched based on smi# going active. 3:0 corresponds to the cycle type, as would be defined by the pci c/be# signals on the pci bus (even though it may not be a real pci cycle). the value is latched based on smi# going active. i/o address: pmbase +50h attribute: r/w (special) default value 01h size: 8-bit lockable: no usage: acpi/legacy power well: core writes to this register initiates an intel ? speedstep ? transition, which involves a temporary transition to a c3-like state in which the stpclk# signal will go active. an intel ? speedstep ? transition always occur on writes to the ss_cnt register, even if the value written to ss_state is the same as the previous value (after this ?transition? the system would still be in the same intel ? speedstep ? state). bit description 7:1 reserved 0 speedstep tm state (ss_state) ? r/w (special). when this bit is read, it will return the current speedstep ? state. writes to this register will cause a change to the speedstep tm state indicated by the value written to this bit. 0 = high-power state. 1 = low-power state. 82801BA ich2 and 82801BAm ich2-m datasheet 9-79 lpc interface bridge registers (d31:f0) 9.9 system management tco registers (d31:f0) the tco logic is accessed via registers mapped to the pci configuration space (device 31:function 0) and the system i/o space. for tco pci configuration registers, see lpc device 31:function 0 pci configuration registers. 9.9.1 tco register i/o map the tco i/o registers reside in a 32-byte range pointed to by a tcobase value, which is, acpibase + 60h in the pci configuration space. the following table shows the mapping of the registers within that 32-byte range. each register is described in the sections below. 9.9.2 tco1_rld?tco timer reload and current value register i/o address: tcobase +00h attribute: r/w default value: 0000h size: 8-bit lockable: no power well: core table 9-11. tco i/o register map offset mnemonic register name: function type 00h tco_rld tco timer reload and current value r/w 01h tco_tmr tco timer initial value r/w 02h tco_dat_in tco data in r/w 03h tco_dat_out tco data out r/w 04h?05h tco1_sts tco status r/w 06h?07h tco2_sts tco status r/w 08h?09h tco1_cnt tco control r/w 0ah?0bh tco2_cnt tco control r/w 0ch?0dh tco_message1, tco_message2 used by bios to indicate post/boot progress r/w 0eh tco_wdstatus watchdog status register r/w 0fh reserved ro 10h sw_irq_gen software irq generation register r/w 11h?1fh reserved ro bit description 7:0 tco timer value. reading this register will return the current count of the tco timer. writing any value to this register will reload the timer to prevent the time-out. bits 7:6 will always be 0. lpc interface bridge registers (d31:f0) 9-80 82801BA ich2 and 82801BAm ich2-m datasheet 9.9.3 tco1_tmr?tco timer initial value register i/o address: tcobase +01h attribute: r/w default value: 0004h size: 8-bit lockable: no power well: core 9.9.4 tco1_dat_in?tco data in register i/o address: tcobase +02h attribute: r/w default value: 0000h size: 8-bit lockable: no power well: core 9.9.5 tco1_dat_out?tco data out register i/o address: tcobase +03h attribute: r/w default value: 0000h size: 8-bit lockable: no power well: core 9.9.6 tco1_sts?tco1 status register i/o address: tcobase +04h attribute: r/wc ro default value: 0000h size: 16-bit lockable: no power well: core (except bit 7, in rtc) bit description 7:6 reserved 5:0 tco timer initial value. value that is loaded into the timer each time the tco_rld register is written. values of 0h?3h will be ignored and should not be attempted. the timer is clocked at approximately 0.6 seconds, and this allows time-outs ranging from 2.4 seconds to 38 seconds. bit description 7:0 tco data in value. data register for passing commands from the os to the smi handler. writes to this register will cause an smi and set the os_tco_smi bit in the tco_sts register. bit description 7:0 tco data out value. data register for passing commands from the smi handler to the os. writes to this register will set the tco_int_sts bit in the tco_sts register. it will also cause an interrupt, as selected by the tco_int_sel bits. bit description 15:13 reserved 12 hub interface serr status (hubserr_sts) ?r/wc. 1 = ich2 received an serr# message via the hub interface. the software must read the memory controller hub (or its equivalent) to determine the reason for the serr#. 0 = software clears this bit by writing a 1 to the bit position. 11 hub interface nmi status (hubnmi_sts) ?r/wc. 1 = ich2 received an nmi message via the hub interface. the software must read the memory controller hub (or its equivalent) to determine the reason for the nmi. 0 = software clears this bit by writing a 1 to the bit position. 82801BA ich2 and 82801BAm ich2-m datasheet 9-81 lpc interface bridge registers (d31:f0) 10 hub interface smi status (hubsmi_sts) ?r/wc. 1 = ich2 received an smi message via the hub interface. the software must read the memory controller hub (or its equivalent) to determine the reason for the smi#. 0 = software clears this bit by writing a 1 to the bit position. 9 hub interface sci status (hubsci_sts) ?r/wc. 1 = ich2 received an sci message via the hub interface. the software must read the memory controller hub (or its equivalent) to determine the reason for the sci. 0 = software clears this bit by writing a 1 to the bit position. 8 bios write status (bioswr_sts) ?r/wc. 1 = ich2 sets this bit and generates and smi# to indicate an illegal attempt to write to the bios. this occurs when either: a) the bioswp bit is changed from 0 to 1 and the bld bit is also set, or b) any write is attempted to the bios and the bioswp bit is also set. 0 = software clears this bit by writing a 1 to the bit position. note:on write cycles attempted to the 4 mb lower alias to the bios space, the bioswr_sts will not be set. 7 new century status (newcentury_sts) ?r/wc. this bit is in the rtc well. 1 = this bit is set when the year byte (rtc i/o space, index offset 09h) rolls over from 99 to 00. setting this bit will cause an smi# (but not a wake event). 0 = cleared by writing a 1 to the bit position or by rtcrst# going active. note that the newcentury_sts bit is not valid when the rtc battery is first installed (or when rtc power has not been maintained). software can determine if rtc power has not been maintained by checking the rtc_pwr_sts bit or by other means (e.g., a checksum on rtc ram). if rtc power is determined to have not been maintained, bios should set the time to a legal value and then clear the newcentury_sts bit. the newcentury_sts bit may take up to 3 rtc clocks for the bit to be cleared after a ?1? is written to the bit to clear it. after writing a ?1? to this bit, software should not exit the smi handler until verifying that the bit has actually been cleared. this will ensure that the smi is not re-entered. 6:4 reserved 3 time out status (timeout) ?r/wc. 1 = set by ich2 to indicate that the smi was caused by the tco timer reaching 0. 0 = software clears this bit by writing a 1 to the bit position. 2 tco interrupt status (tco_int_sts) ?r/wc. 1 = smi handler caused the interrupt by writing to the tco_dat_out register. 0 = software clears this bit by writing a 1 to the bit position. 1 software tco smi status (sw_tco_smi) ?r/wc. 1 = software caused an smi# by writing to the tco_dat_in register. 0 = software clears this bit by writing a 1 to the bit position. 0 nmi to smi status (nmi2smi_sts) ?ro. 1 = set by the ich2 when an smi# occurs because an event occurred that would otherwise have caused an nmi (because nmi2smi_en is set). 0 = cleared by clearing the associated nmi status bit. bit description lpc interface bridge registers (d31:f0) 9-82 82801BA ich2 and 82801BAm ich2-m datasheet 9.9.7 tco2_sts?tco2 status register i/o address: tcobase +06h attribute: r/wc, ro default value: 0000h size: 16-bit lockable: no power well: resume (except bit 0, in rtc) bit description 15:3 reserved 2 boot status (boot_sts): 1 = set to 1 when the second_to_sts bit goes from 0 to 1 and the processor has not fetched the first instruction. 0 = cleared by ich2 based on rsmrst# or by software writing a 1 to this bit. note that software should first clear the second_to_sts bit before writing a 1 to clear the boot_sts bit. if rebooting due to a second tco timer time-out and if the boot_sts bit is set, the ich2 will reboot using the ?safe? multiplier (1111). this allows the system to recover from a processor fr equency multiplier that is too high, and allows the bios to check the boot_sts bit at boot. if the bit is set and the frequency multiplier is 1111, t hen the bios knows that the processor has been programmed to an illegal multiplier. 1 second tco time-out status (second_to_sts) ?r/wc. 1 = the ich2 sets this bit to a 1 to indicate that the tco timer timed out a second time (probably due to system lock). if this bit is set the ich2 will reboot the system after the second time-out. the reboot is done by asserting pcirst#. 0 = this bit is cleared by writing a 1 to the bit position or by a rsmrst#. 0 intruder detect (intrd_det) ?r/wc. 1 = set by ich2 to indicate that an intrusion was detected. this bit is set even if the system is in g3 state. 0 = this bit is only cleared by writing a 1 to the bit position, or by rtcrst# assertion. 82801BA ich2 and 82801BAm ich2-m datasheet 9-83 lpc interface bridge registers (d31:f0) 9.9.8 tco1_cnt?tco1 control register i/o address: tcobase +08h attribute: r/w, r/wc default value: 0000h size: 16-bit lockable: no power well: core 9.9.9 tco2_cnt?tco2 control register i/o address: tcobase +0ah attribute: r/w default value: 0000h size: 16-bit lockable: no power well: resume bit description 15:12 reserved 11 tco timer halt (tco_tmr_hlt)? r/w. 0 = the tco timer is enabled to count. 1 = the tco timer will halt. it will not count and, thus, cannot reach a value that will cause an smi# or set the second_to_sts bit. when set, this bit prevents rebooting and prevents alert on lan event messages from being transmitted on the smlink (but not alert on lan heartbeat messages). 10 send now (sendnow) ?r/w (special). 1 = writing a 1 to this bit will cause the ich to send an alert on lan event message over the smlink interface, with the software event bit set. 0 = the ich will clear this bit when it has completed sending the message. software must not set this bit to 1 again until the ich has set it back to 0. setting the sendnow bit causes the ich2 integrated lan controller to reset, which can have unpredictable side-effects. unless software protects against these side effects, software should not attempt to set this bit. 9 nmi to smi enable (nmi2smi_en) ?r/w. 0 = normal nmi functionality. 1 = forces all nmis to instead cause smis. the functionality of this bit is dependent upon the settings of the nmi_en bit and the gbl_smi_en bit as detailed in the following table: nmi_en gbl_smi_en description 0 0 no smi# at all because gbl_smi_en = 0 0 1 smi# will be caused due to nmi events 1 0 no smi# at all because gbl_smi_en = 0 1 1 no smi# due to nmi because nmi_en = 1 8 nmi now (nmi_now) ?r/wc. 1 = writing a 1 to this bit causes an nmi. this allows the bios or smi handler to force an entry to the nmi handler. 0 = this bit is cleared by writing a 1 to the bit position. the nmi handler is expected to clear this bit. another nmi will not be generated until the bit is cleared. 7:0 reserved bit description 15:3 reserved. 2:1 intruder# signal select (intrd_sel) ?r/w. selects the action to take if the intruder# signal goes active. 00 = no interrupt or smi# 01 = interrupt (as selected by tco_int_sel). 10 = smi 11 = reserved 0 reserved. lpc interface bridge registers (d31:f0) 9-84 82801BA ich2 and 82801BAm ich2-m datasheet 9.9.10 tco_message1 and tco_message2 registers i/o address: tcobase +0ch (message 1) attribute: r/w tcobase +0dh (message 2) default value: 00h size: 8-bit lockable: no power well: resume 9.9.11 tco_wdstatus?tco2 control register offset address: tcobase + 0eh attribute: r/w default value: 00h size: 8 bits power well: resume 9.9.12 sw_irq_gen?software irq generation register offset address: tcobase + 10h attribute: r/w default value: 03h size: 8 bits power well: resume bit description 7:0 tco message (tco_message[ n ]) ?r/w.the value written into this register will be sent out via the smlink interface in the message field of the alert on lan message. bios can write to this register to indicate its boot progress which can be monitored externally. bit description 7:0 watchdog status (wdstatus) ?r/w. the value written to this register will be sent in the alert on lan message on the smlink interface. it can be used by the bios or system management software to indicate more details on the boot progress. this register will be reset to the default of 00h based on rsmrst# (but not pci reset). bit description 7:2 reserved. 1 irq12 cause (irq12_cause) ?r/w. the state of this bit is logically anded with the irq12 signal as received by the ich2?s serirq logic. this bit must be a ?1? (default) if the ich2 is expected to receive irq12 assertions from a serirq device. 0 irq1 cause (irq1_cause) ?r/w. the state of this bit is logically anded with the irq1 signal as received by the ich2?s serirq logic. this bit must be a ?1? (default) if the ich2 is expected to receive irq1 assertions from a serirq device. 82801BA ich2 and 82801BAm ich2-m datasheet 9-85 lpc interface bridge registers (d31:f0) 9.10 general purpose i/o registers (d31:f0) the control for the general purpose i/o signals is handled through a separate 64-byte i/o space. the base offset for this space is selected by the gpio_bar register. table 9-12 summarizes the ich2 gpio implementation. table 9-12. summary of gpio implementation gpio type alternate function (note 1) power well notes gpio[0] input only req[a]# core gpio_use_sel bit 0 enables req/gnt[a]# pair. input active status read from gpe1_sts register bit 0. input active high/low set through gpi_inv register bit 0. gpio[1] input only req[b]# or req[5]# core gpio_use_sel bit 1 enables req/gnt[b]# pair (see note 4). input active status read from gpe1_sts register bit 1. input active high/low set through gpi_inv register bit 1. gpio[2] n/a n/a n/a not implemented gpio[3:4] input only pirq[e:h]# core gpio_use_sel bits [3:4] enable pirq[f:g]#. input active status read from gpe1_sts reg. bits [3:4]. input active high/low set through gpi_inv reg. bit [3:4]. gpio[5] n/a n/a n/a not implemented gpio[6] input only unmuxed core ich2 (82801BA): input active status read from gpe1_sts register bit 6. input active high/low set through gpi_inv register bit 6. ich2-m (82801BAm): not implemented. gpio[7] input only unmuxed core input active status read from gpe1_sts register bit 7. input active high/low set through gpi_inv register bit 7 gpio[8] input only unmuxed resume input active status read from gpe1_sts register bit 8. input active high/low set through gpi_inv register bit 8. gpio[9:10] n/a n/a n/a not implemented gpio[11] input only smbalert# resume gpio_use_sel bit 11 enables smbalert# input active status read from gpe1_sts register bit 11. input active high/low set through gpi_inv register bit 11. gpio[12] input only unmuxed resume input active status read from gpe1_sts register bit 12. input active high/low set through gpi_inv register bit 12. gpio[13] input only unmuxed resume input active status read from gpe1_sts register bit 13. input active high/low set through gpi_inv register bit 13. gpio[14:15] n/a n/a n/a not implemented gpio[16] output only gnt[a]# core output controlled via gp_lvl register bit 16. ttl driver output gpio[17] output only gnt[b]# or gnt[5]# core output controlled via gp_lvl register bit 17. ttl driver output gpio[18:19] output only unmuxed core ich2 (82801BA): output controlled via gp_lvl register bits [18:19]. ttl driver output ich2-m (82801BAm): not implemented. lpc interface bridge registers (d31:f0) 9-86 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. all gpios default to their alternate function 2. all inputs are sticky. the status bit will remain set as long as the input was asserted for 2 clocks. gpis are sampled on pci clocks in s0/s1... 4. gpio[7:6,4:3,1:0] (gpio[7,4:3,1:0] for the ich2-m) are 5v tolerant, and all gpis can be routed to cause an sci or smi# 5. if gpio_use_sel bit 1 is set to 1 and gen_cnt bit 25 is also set to 1 then req/gnt[5]# is enabled. see section 9.1.22 . gpio[20] output only unmuxed core ich2 (82801BA): output controlled via gp_lvl register bit 20. ttl driver output ich2-m (82801BAm): not implemented. gpio[21] output only unmuxed for ich2 82801BA cs_stat# for ich2-m 82801BAm core ich2 (82801BA): this gpo defaults high. output controlled via gp_lvl register bit 21. ttl driver output ich2-m (82801BAm): output controlled via gp_lvl register bit 21. ttl driver output gpio[22] output only unmuxed core ich2 (82801BA): output controlled via gp_lvl register bit [22]. open-drain output ich2-m (82801BAm): not implemented. gpio[23] output only unmuxed core ich2 (82801BA): output controlled via gp_lvl register bit [23]. ttl driver output ich2-m (82801BAm): not implemented. gpio[24] input / output unmuxed resume ich2 (82801BA): input active status read from gp_lvl register bit 24. output controlled via gp_lvl register bit 24. ttl driver output ich2-m (82801BAm): not implemented. gpio[25] input / output unmuxed resume blink enabled via gpo_blink register bit 25. input active status read from gp_lvl register bit 25 output controlled via gp_lvl register bit 25. ttl driver output gpio[26] n/a n/a n/a not implemented gpio[27:28] input / output unmuxed resume input active status read from gp_lvl register bits [27:28] output controlled via gp_lvl register bits [27:28] ttl driver output gpio[29:31] n/a n/a n/a not implemented table 9-12. summary of gpio implementation (continued) gpio type alternate function (note 1) power well notes 3. gpis are sampled on rtc clocks in s3/s4/s5 for the 82801BA ich2 and in s1/s3/s4/s5 for the 82801BAm ich2-m. 82801BA ich2 and 82801BAm ich2-m datasheet 9-87 lpc interface bridge registers (d31:f0) 9.10.1 gpio register i/o address map 9.10.2 gpio_use_sel?gpio use select register offset address: gpiobase + 00h attribute: r/w default value: 1a003180h size: 32-bit lockable: yes power well: resume table 9-13. registers to control gpio offset mnemonic register name default access general registers 00?03h gpio_use_sel gpio use select 1a00 3180h r/w 04?07h gp_io_sel gpio input/output select 0000 ffffh r/w 08?0bh ? reserved 00h ro 0c?0fh gp_lvl gpio level for input or output 1f1f 0000h r/w 10?13h ? reserved 00h ro output control registers 14?17h gpo_ttl gpio ttl select 06630000h ro 18?1bh gpo_blink gpio blink enable 00000000h r/w 1c?1fh ? reserved 0 ro input control registers 20?2bh ? reserved 00000000h ro 2c?2fh gpi_inv gpio signal invert 00000000h r/w bit description 21,11, 5:0 gpio use select (gpio_use_sel) ?r/w. each bit in this register enables the corresponding gpio (if it exists) to be used as a gpio, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. note: ich2 82801BA: bits 31:29, 26, 15:14, 10:9 and 7 are not implemented because there is no corresponding gpio. ich2-m 82801BAm: bits 31:29, 26, 24:22, 20:18, 15:14, 10:9, and 7:6 are not implemented because there is no corresponding gpio. note: ich2 82801BA: bits 28:27, 25:22, 20:18,13:12, 8 and 6 are not implemented because the corresponding gpios are not multiplexed. ich2-m 82801BAm: bits 28:27, 25, 13:12 and 8 are not implemented because the corresponding gpios are not mutiplexed. lpc interface bridge registers (d31:f0) 9-88 82801BA ich2 and 82801BAm ich2-m datasheet 9.10.3 gp_io_sel?gpio input/output select register offset address: gpiobase +04h attribute: r/w default value: 0000ffffh size: 32-bit lockable: no power well: resume notes: 1. there will be some delay on gpio[24:28] going to their default state based on the rising edge of rsmrst#. this is the case since these signals are in the resume well and resume well outputs are not valid until after rsmrst# goes high. ich2 only guarantees that these gpios will be stable prior to slp_s3# going active. bit description 31:29, 26 15:14, 10:9, 5, 2 reserved. 28:27,25:24 (ich2) 28:27,25 (ich2-m) gpio[n] select (gpio[n]_sel) ?r/w. 0 = output. the corresponding gpio signal is an output. 1 = input. the corresponding gpio signal is an input. 24:22, 20:18, 6 (ich2-m) reserved 23:16 (ich2) 21:16 (ich2-m) always 0. the gpios are fixed as outputs. 13:11, 8:6, 4:3, 1:0 (ich2) 13:11, 8:7, 4:3, 1:0 (ich2-m) always 1. these gpios are fixed as inputs. 82801BA ich2 and 82801BAm ich2-m datasheet 9-89 lpc interface bridge registers (d31:f0) 9.10.4 gp_lvl?gpio level for input or output register offset address: gpiobase +0ch attribute: r/w, ro default value: 1b3f 0000h size: 32-bit lockable: no power well: see bit descriptions bit description 31:29, 26, 15:14, 10:9, 5, 2 (ich2) 31:29, 26, 24:22, 20:18, 15:14, 10:9 6, 5, 2 (ich2-m) reserved. 28:27, 25:24 (ich2) 28:27, 25 (ich2-m) gpio level (gp_lvl[n])? r/w. if gpio[n] is programmed to be an output (via the corresponding bit in the gp_io_sel register), then the bit can be updated by software to drive a high or low value on the output pin. if gpio[n] is programmed as an input, then software can read the bit to determine the level on the corresponding input pin. these bits correspond to gpio that are in the resume well, and will be reset to their default values by rsmrst# but not by pcirst#. 0 = low 1 = high 23:16 (ich2) 21, 17:16 (ich2-m) gpio level (gp_lvl[n])? r/w. these bits can be updated by software to drive a high or low value on the output pin. these bits correspond to gpio that are in the core well, and will be reset to their default values by pcirst#. 0 = low 1 = high 13:11, 8:6, 4:3, 1:0 (ich2) 13:11, 8:7, 4:3, 1:0 (ich2-m) ich2 82801BA: for gpi[13:11] and [8:6,4:3,1:0], the active status of a gpi is read from the corresponding bit in gpe1_sts register. ich2-m 82801BAm: for gpi[13:11] and [8:7,4:3,1:0], the active status of a gpi is read from the corresponding bit in gpe1_sts register. lpc interface bridge registers (d31:f0) 9-90 82801BA ich2 and 82801BAm ich2-m datasheet 9.10.5 gpo_blink?gpo blink enable register offset address: gpiobase +18h attribute: r/w default value: 0004 0000h size: 32-bit lockable: no power well: see bit description notes: . bit description 31:29, 26, 24:20, 17:0 (ich2) 31:29, 26, 24:20, 18:0 (ich2-m) reserved 28:27, 25 gpio blink (gp_blink[n])? r/w. the setting of these bits will have no effect if the corresponding gpio is programmed as an input. these bits correspond to gpio that are in the resume well and will be reset to their default values by rsmrst# but not by pcirst#. 0 = the corresponding gpio will function normally. 1 = if the corresponding gpio is programmed as an output, the output signal will blink at a rate of approximately once per second. the high and low times have approximately 50% duty cycle. the gp_lvl bit is not altered when this bit is set. 19:18 (ich2) 19 (ich2-m) gpio blink (gp_blink[n])? r/w. the setting of these bits will have no effect if the corresponding gpio is programmed as an input. these bits correspond to gpio that are in the core well, and will be reset to their default values by pcirst#. 0 = the corresponding gpio will function normally. 1 = if the corresponding gpio is programmed as an output, the output signal will blink at a rate of approximately once per second. the high and low times have approximately 50% duty cycle. the gp_lvl bit is not altered when this bit is set. 1. ich2 82801BA: gpio[18] blinks, by default, immediately after reset. this signal could be connected to an led to indicate a failed boot (by programming bios to clear gp_blink[18] after successful post). 82801BA ich2 and 82801BAm ich2-m datasheet 9-91 lpc interface bridge registers (d31:f0) 9.10.6 gpi_inv?gpio signal invert register offset address: gpiobase +2ch attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: see bit description bit description 31:14, 10:9, 5, 2 (ich2) 31:14, 10:9, 6, 5, 2 (ich2-m) reserved 13:11, 8 gpio signal high/low select (gp_inv[n])? r/w. these bits are used to allow both active- low and active-high inputs to cause smi# or sci. note that in the s0 or s1 state, the input signal must be active for at least 2 pci clocks to ensure detection by the ich2. in the s3, s4 or s5 states the input signal must be active for at least 2 rtc clocks to ensure detection. the setting of these bits will have no effect if the corresponding gpio is programmed as an output. these bits correspond to gpio that are in the resume well, and will be reset to their default values by rsmrst# but not by pcirst#. 0 = the corresponding gpi_sts bit will be set when the ich2 detects the state of the input pin to be high. 1 = the corresponding gpi_sts bit will be set when the ich2 detects the state of the input pin to be low. 7:6, 4:3, 1:0 (ich2) 7, 4:3, 1:0 (ich2-m) gpio signal high/low select (gp_inv[n])? r/w. these bits are used to allow both active- low and active-high inputs to cause smi# or sci. note that in the s0 or s1 state, the input signal must be active for at least 2 pci clocks to ensure detection by the ich2. the setting of these bits will have no effect if the corresponding gpio is programmed as an output. these bits correspond to gpio that are in the core well, and will be reset to their default values by pcirst#. 0 = the corresponding gpi_sts bit will be set when the ich2 detects the state of the input pin to be high. 1 = the corresponding gpi_sts bit will be set when the ich2 detects the state of the input pin to be low. lpc interface bridge registers (d31:f0) 9-92 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank 82801BA ich2 and 82801BAm ich2-m datasheet 10-1 ide controller registers (d31:f1) ide controller registers (d31:f1) 10 10.1 pci configuration registers (ide?d31:f1) note: registers that are not shown should be treated as reserved (see section 6.2 for details). all of the ide registers are in the core well. none can be locked. notes: 1. refer to the specification update for the value of the revision id register 2. the ich2 ide controller is not arbitrated as a pci device; therefore, it doe s not need a master latency timer. table 10-1. pci configuration map (ide?d31:f1) offset mnemonic register name/function default type 00h?01h vid vendor id 8086h ro 02h?03h did device id 244bh (ich2) 244ah (ich2-m) ro 04h?05h cmd command register 00h r/w 06h?07h sts device status 0280h r/w 08h rid revision id see note 1 ro 09h pi programming interface 80h ro 0ah scc sub class code 01h ro 0bh bcc base class code 01h ro 0dh mlt master latency timer 00 ro 0eh htype header type 00h ro 20h?23h bar base address register 00000001h r/w 2c?2dh svid subsystem vendor id 00 r/write- once 2e?2fh sid subsystem id 00 r/write- once 40h?41h ide_timp primary ide timing 0000h r/w 42?43h id_tims secondary ide timing 0000h r/w 44h sidetim slave ide timing 00h r/w 48h sdmac synchronous dma control register 00h r/w 4ah?4bh sdmatim synchronous dma timing register 0000h r/w 54h ide_config ide i/o configuration register 00h r/w ide controller registers (d31:f1) 10-2 82801BA ich2 and 82801BAm ich2-m datasheet 10.1.1 vid?vendor id register (ide?d31:f1) offset address: 00?01h attribute: ro default value: 8086h size: 16-bit lockable: no power well: core 10.1.2 did?device id register (ide?d31:f1) offset address: 02?03h attribute: ro lockable: no size: 16-bit power well: core 10.1.3 cmd?command register (ide?d31:f1) address offset: 04h?05h attribute: ro, r/w default value: 00h size: 16 bits bit description 15:0 vendor id value. this is a 16 bit value assigned to intel. intel vid = 8086h default value: 244bh (82801BA ich2) 244ah (82801BAm ich2-m) bit description 15:0 device id value. this is a 16 bit value assigned to the ich2 ide controller. bit description 15:10 reserved. 9 fast back to back enable (fbe) ? ro. reserved as 0. 8 serr# enable ? ro. reserved as 0. 7 wait cycle control ? ro. reserved as 0. 6 parity error response ? ro. reserved as 0. 5 vga palette snoop ? ro. reserved as 0. 4 postable memory write enable (pmwe) ? ro. reserved as 0. 3 special cycle enable (sce) ? ro. reserved as 0. 2 bus master enable (bme)? r/w. controls the ich2?s ability to act as a pci master for ide bus master transfers. 1 memory space enable (mse) ? ro. reserved as 0. 0 i/o space enable (iose)? r/w. this bit controls access to the i/o space registers. 0 = disables access to the legacy ide ports (both primary and secondary) as well as the bus master io registers. 1 = enable. note that the base address register for the bus master registers should be programmed before this bit is set. note: separate bits are provided (ide decode enable, in the ide timing register) to independently disable the primary or secondary i/o spaces. 82801BA ich2 and 82801BAm ich2-m datasheet 10-3 ide controller registers (d31:f1) 10.1.4 sts?device status register (ide?d31:f1) address offset: 06?07h attribute: r/wc, ro default value: 0280h size: 16 bits 10.1.5 rid?revision id register (hub-pci?d30:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 10.1.6 pi?programming interface (ide?d31:f1) address offset: 09h attribute: ro default value: 80h size: 8 bits bit description 15 detected parity error (dpe) ? ro. reserved as 0. 14 signaled system error (sse) ? ro. reserved as 0. 13 received master-abort status (rma)? r/wc. 1 = bus master ide interface function, as a master, generated a master abort. 0 = cleared by writing a 1 to it. 12 reserved as 0 ? ro. 11 signaled target-abort status (sta)? r/wc. 1 = ich2 ide interface function is targeted with a transaction that the ich2 terminates with a target abort. 0 = cleared by writing a 1 to it. 10:9 devsel# timing status (devt)? ro. 01 = hardwired; however, the ich2 does not have a real devsel# signal associated with the ide unit, so these bits have no effect. 8 data parity error detected ? ro. reserved as 0. 7 fast back-to-back capable ? ro. reserved as 1. 6 user definable features (udf) ? ro. reserved as 0. 5 66 mhz capable ? ro. reserved as 0. 4:0 reserved bit description 7:0 revision identification number ?ro. this 8-bit value indicates the revision number for the ich2 ide controller. refer to the specification update for the value of the revision id register. bit description 7:0 programming interface value? ro. 80h = the 1b in bit 7 indicates that this ide controller is capable of bus master operation. ide controller registers (d31:f1) 10-4 82801BA ich2 and 82801BAm ich2-m datasheet 10.1.7 scc?sub class code (ide?d31:f1) address offset: 0ah attribute: ro default value: 01h size: 8 bits 10.1.8 bcc?base class code (ide?d31:f1) address offset: 0bh attribute: ro default value: 01h size: 8 bits 10.1.9 mlt?master latency timer (ide?d31:f1) address offset: 0dh attribute: ro default value: 00h size: 8 bits 10.1.10 bm_base?bus master base address register (ide?d31:f1) address offset: 20h?23h attribute: r/w default value: 00000001h size: 32 bits the bus master ide interface function uses base address register 5 to request a 16 byte io space to provide a software interface to the bus master functions. only 12 bytes are actually used (6 bytes for primary, 6 bytes for secondary). only bits [15:4] are used to decode the address. bit description 7:0 sub class code? ro. 01h = ide device, in the context of a mass storage device. bit description 7:0 base class code? ro. 01 = mass storage device bit description 7:0 bus master latency ? ro. the ide controller is implemented internally, and is not arbitrated as a pci device, so it does not need a master latency timer. hardwired to 00h. bit description 31:16 reserved. 15:4 base address? r/w. base address of the i/o space (16 consecutive i/o locations). 3:1 reserved. 0 resource type indicator (rte)? ro. hardwired to 1, indicating a request for io space. 82801BA ich2 and 82801BAm ich2-m datasheet 10-5 ide controller registers (d31:f1) 10.1.11 ide_svid?subsystem vendor id (ide?d31:f1) address offset: 2ch?2dh attribute: r/write-once default value: 00h size: 16 bits lockable: no power well: core 10.1.12 ide_sid?subsystem id (ide?d31:f1) address offset: 2eh?2fh attribute: r/write-once default value: 00h size: 16 bits lockable: no power well: core 10.1.13 ide_tim?ide timing register (ide?d31:f1) address offset: primary: 40?41h attribute: r/w secondary: 42?43h default value: 0000h size: 16 bits this register controls the timings driven on the ide cable for pio and 8237 style dma transfers. it also controls operation of the buffer for pio transfers. bit description 15:0 subsystem vendor id (svid)? r/write-once. the svid register, in combination with the subsystem id (sid) register, enables the operating system (os) to distinguish subsystems from each other. software (bios) sets the value in this register. after that, the value can be read, but subsequent writes to this register have no effect. the value written to this register will also be readable via the corresponding svid registers for the usb#1, usb#2 and smbus functions. bit description 15:0 subsystem id (sid)? r/write-once. the sid register, in combination with the svid register, enables the operating system (os) to distinguish subsystems from each other. software (bios) sets the value in this register. after that, the value can be read, but subsequent writes to this register have no effect. the value written to this register will also be readable via the corresponding sid registers for the usb#1, usb#2 and smbus functions. bit description 15 ide decode enable (ide)? r/w. individually enable/disable the primary or secondary decode. the ide i/o space enable bit in the command register must be set in order for this bit to have any effect. additionally, separate configuration bits are provided (in the ide i/o configuration register) to individually disable the primary or secondary ide interface signals, even if the ide decode enable bit is set. 0 = disable. 1 = enables the ich2 to decode the associated command blocks (1f0h?1f7h for primary, 170h?177h for secondary) and control block (3f6h for primary and 376h for secondary). 14 drive 1 timing register enable (sitre)? r/w. 0 = use bits 13:12, 9:8 for both drive 0 and drive 1. 1 = use bits 13:12, 9:8 for drive 0, and use the slave ide timing register for drive 1 13:12 iordy sample point (isp). the setting of these bits determine the number of pci clocks between ide ior#/iow# assertion and the first iordy sample point. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved ide controller registers (d31:f1) 10-6 82801BA ich2 and 82801BAm ich2-m datasheet 11:10 reserved. 9:8 recovery time (rct)? r/w. the setting of these bits determines the minimum number of pci clocks between the last iordy sample point and the ior#/iow# strobe of the next cycle. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clock 7 drive 1 dma timing enable (dte1)? r/w. 0 = disable. 1 = enable the fast timing mode for dma transfers only for this drive. pio transfers to the ide data port will run in compatible timing. 6 drive 1 prefetch/posting enable (ppe1)? r/w. 0 = disable. 1 = enable prefetch and posting to the ide data port for this drive. 5 drive 1 iordy sample point enable (ie1)? r/w. 0 = disable iordy sampling for this drive. 1 = enable iordy sampling for this drive. 4 drive 1 fast timing bank (time1)? r/w. 0 = accesses to the data port will use compatible timings for this drive. 1 = when this bit = 1 and bit 14 = 0, accesses to the data port will use bits 13:12 for the iordy sample point, and bits 9:8 for the recovery time. when this bit = 1 and bit 14 = 1, accesses to the data port will use the iordy sample point and recover time specified in the slave ide timing register. 3 drive 0 dma timing enable (dte0)? r/w. 0 = disable. 1 = enable fast timing mode for dma transfers only for this drive. pio transfers to the ide data port will run in compatible timing. 2 drive 0 prefetch/posting enable (ppe0)? r/w. 0 = disable prefetch and posting to the ide data port for this drive. 1 = enable prefetch and posting to the ide data port for this drive. 1 drive 0 iordy sample point enable (ie0)? r/w. 0 = disable iordy sampling is disabled for this drive. 1 = enable iordy sampling for this drive. 0 drive 0 fast timing bank (time0)? r/w. 0 = accesses to the data port will use compatible timings for this drive. 1 = accesses to the data port will use bits 13:12 for the iordy sample point, and bits 9:8 for the recovery time bit description 82801BA ich2 and 82801BAm ich2-m datasheet 10-7 ide controller registers (d31:f1) 10.1.14 slv_idetim?slave (drive 1) ide timing register (ide?d31:f1) address offset: 44h attribute: r/w default value: 00h size: 8 bits bit description 7:6 secondary drive 1 iordy sample point (sisp1)? r/w. determines the number of pci clocks between ide ior#/iow# assertion and the first iordy sample point, if the access is to drive 1 data port and bit 14 of the ide timing register for secondary is set. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved 5:4 secondary drive 1 recovery time (srct1)? r/w. determines the minimum number of pci clocks between the last iordy sample point and the ior#/iow# strobe of the next cycle, if the access is to drive 1 data port and bit 14 of the ide timing register for secondary is set. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clocks 3:2 primary drive 1 iordy sample point (pisp1)? r/w. determines the number of pci clocks between ior#/iow# assertion and the first iordy sample point, if the access is to drive 1 data port and bit 14 of the ide timing register for primary is set. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved 1:0 primary drive 1 recovery time (prct1)? r/w. determines the minimum number of pci clocks between the last iordy sample point and the ior#/iow# strobe of the next cycle, if the access is to drive 1 data port and bit 14 of the ide timing register for primary is set. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clocks ide controller registers (d31:f1) 10-8 82801BA ich2 and 82801BAm ich2-m datasheet 10.1.15 sdma_cnt?synchronous dma control register (ide?d31:f1) address offset: 48h attribute: r/w default value: 00h size: 8 bits 10.1.16 sdma_tim?synchronous dma timing register (ide?d31:f1) address offset: 4a?4bh attribute: r/w default value: 0000h size: 16 bits bit description 7:4 reserved. 3 secondary drive 1 synchronous dma mode enable (ssde1)? r/w. 0 = disable (default). 1 = enable synchronous dma mode for secondary channel drive 1 2 secondary drive 0 synchronous dma mode enable (ssde0)? r/w. 0 = disable (default). 1 = enable synchronous dma mode for secondary drive 0. 1 primary drive 1 synchronous dma mode enable (psde1)? r/w. 0 = disable (default). 1 = enable synchronous dma mode for primary channel drive 1 0 primary drive 0 synchronous dma mode enable (psde0)? r/w. 0 = disable (default). 1 = enable synchronous dma mode for primary channel drive 0 bit description 15:14 reserved. 13:12 secondary drive 1 cycle time (sct1)? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. scb1 = 0 (33 mhz clk) scb1 = 1 (66 mhz clk) fast_scb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clks, rp 16 clks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved 11:10 reserved. 9:8 secondary drive 0 cycle time (sct0)? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. scb1 = 0 (33 mhz clk) scb1 = 1 (66 mhz clk) fast_scb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clks, rp 16 clks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved 7:6 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 10-9 ide controller registers (d31:f1) 10.1.17 ide_config?ide i/o configuration register address offset: 54h attribute: r/w default value: 00h size: 32 bits 5:4 primary drive 1 cycle time (pct1)? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. pcb1 = 0 (33 mhz clk) pcb1 = 1 (66 mhz clk) fast_pcb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clks, rp 16 clks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved 3:2 reserved. 1:0 primary drive 0 cycle time (pct0)? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. pcb1 = 0 (33 mhz clk) pcb1 = 1 (66 mhz clk) fast_pcb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clks, rp 16 clks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved bit description bit description 31:20 reserved. 19:18 secondary ide signal mode (sec_sig_mode) ?r/w. 00 = normal (enabled). 01 = tri-state (disabled). 10 = drive low (disabled). 11 = reserved. ich2 (82801BA): these bits are used to control mode of the secondary ide signal pins. these bits should always be set to 00b for desktop implementations. ich2-m (82801BAm): these bits are used to control mode of the secondary ide signal pins for mobile swap bay support. 17:16 primary ide signal mode (prim_sig_mode) ?r/w. 00 = normal (enabled). 01 = tri-state (disabled). 10 = drive low (disabled). 11 = reserved. ich2 (82801BA): these bits are used to control mode of the primary ide signal pins. these bits should always be set to 00b for desktop implementations. ich2-m (82801BAm): these bits are used to control mode of the secondary ide signal pins for mobile swap bay support. 15 fast secondary drive 1 base clock (fast_scb1) ?r/w. this bit is used in conjuction with the sct1 bits to enable/disable ultra ata/100 timings for the secondary slave drive. 0 = disable ultra ata/100 timing for the secondary slave drive. 1 = enable ultra ata/100 timing for the secondary slave drive (overrides bit 3 in this register). ide controller registers (d31:f1) 10-10 82801BA ich2 and 82801BAm ich2-m datasheet 14 fast secondary drive 0 base clock (fast_scb0) ?r/w. this bit is used in conjuction with the sct0 bits to enable/disable ultra ata/100 timings for the secondary master drive. 0 = disable ultra ata/100 timing for the secondary master drive. 1 = enable ultra ata/100 timing for the secondary master drive (overrides bit 2 in this register). 13 fast primary drive 1 base clock (fast_pcb1) ?r/w. this bit is used in conjuction with the pct1 bits to enable/disable ultra ata/100 timings for the primary slave drive. 0 = disable ultra ata/100 timing for the primary slave drive. 1 = enable ultra ata/100 timing for the primary slave drive (overrides bit 1 in this register). 12 fast primary drive 0 base clock (fast_pcb0) ?r/w. this bit is used in conjuction with the pct0 bits to enable/disable ultra ata/100 timings for the primary master drive. 0 = disable ultra ata/100 timing for the primary master drive. 1 = enable ultra ata/100 timing for the primary master drive (overrides bit 0 in this register). 11 reserved. 10 write buffer pingpong enable (wr_pingpong_en) ?r/w. 0 = disabled. the buffer will behave similar to piix4. 1 = enables the write buffer to be used in a split (ping/pong) manner. 9:8 reserved. 7 secondary slave channel cable reporting ?r/w. bios should program this bit to tell the ide driver which cable is plugged into the channel. 0 = 40 conductor cable is present. 1 = 80 conductor cable is present. 6 secondary master channel cable reporting? r/w. same description as bit 7 5 primary slave channel cable reporting? r/w. same description as bit 7 4 primary master channel cable reporting? r/w. same description as bit 7 3 secondary drive 1 base clock (scb1) ?r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 2 secondary drive 0 base clock (scbo) ?r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 1 primary drive 1 base clock (pcb1) ?r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 0 primary drive 0 base clock (pcb0) ?r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings bit description 82801BA ich2 and 82801BAm ich2-m datasheet 10-11 ide controller registers (d31:f1) 10.2 bus master ide i/o registers (d31:f1) the bus master ide function uses 16 bytes of i/o space, allocated via the bmiba register, located in device 31:function 1 configuration space (offset 20h). all bus master ide i/o space registers can be accessed as byte, word, or dword quantities. reading reserved bits returns an indeterminate, inconsistent value; writes to reserved bits have no affect (but should not be attempted). the description of the i/o registers is shown in table 10-2 . 10.2.1 bmic[p,s]?bus master ide command register address offset: primary: 00h attribute: r/w secondary: 08h default value: 00h size: 8 bits table 10-2. bus master ide i/o registers offset mnemonic register default type 00h bmicp command register primary 00h r/w 01h reserved 00h ro 02h bmisp status register primary 00h r/wc 03h reserved 00h ro 04h?07h bmidp descriptor table pointer primary xxxxxxxxh r/w 08h bmics command register secondary 00h r/w 09h reserved 00h ro 0ah bmiss status register secondary 00h r/wc 0bh reserved 00h ro 0ch?0fh bmids descriptor table pointer secondary xxxxxxxxh r/w bit description 7:4 reserved. returns 0s. 3 read / write control (rwc)? r/w. this bit sets the direction of the bus master transfer: this bit must not be changed when the bus master function is active. 0 = memory reads. 1 = memory writes 2:1 reserved. returns 0s. 0 start/stop bus master (start)? r/w. 1 = enables bus master operation of the controller. bus master operation begins when this bit is detected changing from a zero to a one. the controller will transfer data between the ide device and memory only when this bit is set. master operation can be halted by writing a '0' to this bit. 0 = all state information is lost when this bit is cleared. master mode operation cannot be stopped and then resumed. if this bit is reset while bus master operation is still active (i.e., the bus master ide active bit of the bus master ide status register for that ide channel is set) and the drive has not yet finished its data transfer (the interrupt bit in the bus master ide status register for that ide channel is not set), the bus master command is said to be aborted and data transferred from the drive may be discarded instead of being written to system memory. this bit is intended to be reset after the data transfer is completed, as indicated by either the bus master ide active bit or the interrupt bit of the bus master ide status register for that ide channel being set, or both. ide controller registers (d31:f1) 10-12 82801BA ich2 and 82801BAm ich2-m datasheet 10.2.2 bmis[p,s]?bus master ide status register address offset: primary: 02h attribute: r/wc secondary: 0ah default value: 00h size: 8 bits 10.2.3 bmid[p,s]?bus master ide descriptor table pointer register address offset: primary: 04h attribute: r/w secondary: 0ch default value: all bits undefined size: 32 bits bit description 7 reserved. returns 0. 6 drive 1 dma capable ?r/w. 0 = not capable. 1 = capable. set by device dependent code (bios or device driver) to indicate that drive 1 for this channel is capable of dma transfers, and that the controller has been initialized for optimum performance. the ich2 does not use this bit. it is intended for systems that do not attach bmide to the pci bus. 5 drive 0 dma capable ?r/w. 0 = not capable. 1 = capable. set by device dependent code (bios or device driver) to indicate that drive 0 for this channel is capable of dma transfers and that the controller has been initialized for optimum performance. the ich2 does not use this bit. it is intended for systems that do not attach bmide to the pci bus. 4:3 reserved. returns 0s. 2 interrupt ?r/wc. software can use this bit to determine if an ide device has asserted its interrupt line (irq14 for the primary channel and irq15 for secondary). 1 = set by the rising edge of the ide interrupt line, regardless of whether or not the interrupt is masked in the 8259 or the internal i/o apic. when this bit is read as a one, all data transferred from the drive is visible in system memory. 0 = this bit is cleared by software writing a '1' to the bit position. if this bit is cleared while the interrupt is still active, this bit will remain clear until another assertion edge is detected on the interrupt line. 1 error ?r/wc. 1 = this bit is set when the controller encounters a target abort or master abort when transferring data on pci. 0 = this bit is cleared by software writing a '1' to the bit position. 0 bus master ide active (act) ?ro. 1 = set by the ich2 when the start bit is written to the command register. 0 = this bit is cleared by the ich2 when the last transfer for a region is performed, where eot for that region is set in the region descriptor. it is also cleared by the ich2 when the start bit is cleared in the command register. when this bit is read as a zero, all data transferred from the drive during the previous bus master command is visible in system memory, unless the bus master command was aborted. bit description 31:2 base address of descriptor table (baddr) ?r/w. corresponds to a[31:2]. the descriptor table must be dword aligned. the descriptor table must not cross a 64 kb boundary in memory. 1:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 11-1 usb controller registers usb controller registers 11 11.1 pci configuration registers (d31:f2/f4) note: registers that are not shown should be treated as reserved (see section 6.2 for details). note: refer to the specification update for the value of the revision id register. 11.1.1 vid?vendor identification register (usb?d31:f2/f4) address offset: 00?01h attribute: ro default value: 8086h size: 16 bits table 11-1. pci configuration map (usb?d31:f2/f4) offset mnemonic register name/function function 2 default function 4 default type 00?01h vid vendor id 8086h 8086h ro 02?03h did device id 2442h 2444h ro 04?05h cmd command register 0000h 0000h r/w 06?07h sta device status 0280h 0280h r/w 08h rid revision id see note see note ro 09h pi programming interface 00h 00h ro 0ah scc sub class code 03h 03h ro 0bh bcc base class code 0ch 0ch ro 0eh htype header type 00h 00h ro 20?23h base base address register 00000001h 00000001h r/w 2c?2dh svid subsystem vendor id 00 00 ro 2e?2fh sid subsystem id 00 00 ro 3ch intr_ln interrupt line 00h 00h r/w 3dh intr_pn interrupt pin 03h 03h ro 60h sb_relnum serial bus release number 10h 10h ro c0?c1h usb_legkey usb legacy keyboard/ mouse control 2000h 2000h r/w c4h usb_res usb resume enable 00h 00h r/w bit description 15:0 vendor id value? ro. this is a 16-bit value assigned to intel. usb controller registers 11-2 82801BA ich2 and 82801BAm ich2-m datasheet 11.1.2 did?device identification register (usb?d31:f2/f4) address offset: 02?03h attribute: ro default value: function 2: 2442h size: 16 bits function 4: 2444h 11.1.3 cmd?command register (usb?d31:f2/f4) address offset: 04?05h attribute: r/w default value: 0000h size: 16 bits bit description 15:0 device id value ?ro . this is a 16-bit value assigned to the ich2 usb host controllers bit description 15:10 reserved. 9 fast back to back enable (fbe)?ro. reserved as 0. 8 serr# enable?ro. reserved as 0. 7 wait cycle control?ro. reserved as 0. 6 parity error response?ro. reserved as 0. 5 vga palette snoop?ro. reserved as 0. 4 postable memory write enable (pmwe)?ro. reserved as 0. 3 special cycle enable (sce)?ro. reserved as 0. 2 bus master enable (bme) ?r/w. when set, the ich2 can act as a master on the pci bus for usb transfers. 1 memory space enable (mse)?ro. reserved as 0. 0 i/o space enable (iose) ?r/w. this bit controls access to the i/o space registers. 1 = enable accesses to the usb i/o registers. the base address register for usb should be programmed before this bit is set. 0 = disable 82801BA ich2 and 82801BAm ich2-m datasheet 11-3 usb controller registers 11.1.4 sta?device status register (usb?d31:f2/f4) address offset: 06?07h attribute: r/wc default value: 0280h size: 16 bits 11.1.5 rid?revision identification register (usb?d31:f2/f4) address offset: 08h attribute: ro default value: see bit description size: 8 bits 11.1.6 pi?programming interface (usb?d31:f2/f4) address offset: 09h attribute: ro default value: 00h size: 8 bits bit description 15:14 reserved as ?00b?. read only. 13 received master-abort status (rma) ?r/wc. 1 = usb, as a master, generated a master-abort. 0 = software clears this bit by writing a 1 to the bit location. 12 reserved. always read as 0. 11 signaled target-abort status (sta) ?r/wc. 1 = usb function is targeted with a transaction that the ich2 terminates with a target abort. 0 = software clears this bit by writing a 1 to the bit location. 10:9 devsel# timing status (devt)? ro. this 2-bit field defines the timing for devsel# assertion. these read only bits indicate the ich2's devsel# timing when performing a positive decode. ich2 generates devsel# with medium timing for usb. 8 data parity error detected: reserved as 0. read only. 7 fast back-to-back capable: reserved as 1. read only. 6 user definable features (udf): reserved as 0. read only. 5 66 mhz capable: reserved as 0. read only. 4:0 reserved. bit description 7:0 revision identification. these bits contain device stepping information and are hardwired to the default value. refer to the specification update for the value of the revision id register. bit description 7:0 programming interface?ro. 00h = no specific register level programming interface defined. usb controller registers 11-4 82801BA ich2 and 82801BAm ich2-m datasheet 11.1.7 scc?sub class code register (usb?d31:f2/f4) address offset: 0ah attribute: ro default value: 03h size: 8 bits 11.1.8 bcc?base class code register (usb?d31:f2/f4) address offset: 0bh attribute: ro default value: 0ch size: 8 bits 11.1.9 base?base address register (usb?d31:f2/f4) address offset: 20?23h attribute: r/w default value: 00000001h size: 32 bits 11.1.10 svid?subsystem vendor id (usb?d31:f2/f4) address offset: 2ch?2dh attribute: ro default value: 00h size: 16 bits lockable: no power well: core bit description 7:0 sub class code ?ro. 03h = universal serial bus host controller. bit description 7:0 base class code ?ro. 0ch = serial bus controller. bit description 31:16 reserved. 15:5 base address ?r/w. bits [15:5] correspond to i/o address signals ad [15:5], respectively. this gives 32 bytes of relocatable i/o space. 4:1 reserved. 0 resource type indicator (rte) ?ro. this bit is hardwired to 1 indicating that the base address field in this register maps to i/o space bit description 15:0 subsystem vendor id (svid)? ro. the svid register, in combination with the subsystem id (sid) register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide_svid register. 82801BA ich2 and 82801BAm ich2-m datasheet 11-5 usb controller registers 11.1.11 sid?subsystem id (usb?d31:f2/f4) address offset: 2eh?2fh attribute: ro default value: 00h size: 16 bits lockable: no power well: core 11.1.12 intr_ln?interrupt line register (usb?d31:f2/f4) address offset: 3ch attribute: r/w default value: 00h size: 8 bits 11.1.13 intr_pn?interrupt pin register (usb?d31:f2/f4) address offset: 3dh attribute: ro default value: size: 8 bits 11.1.14 sb_relnum?serial bus release number register (usb?d31:f2/f4) address offset: 60h attribute: ro default value: 10h size: 8 bits bit description 15:0 subsystem id (sid)? r/write-once. the sid register, in combination with the svid register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide_sid register. bit description 7:0 interrupt line ?r/w. this data is not used by the ich2. it is to communicate to software the interrupt line that the interrupt pin is connected to. default value: function 2: 03h(82801BA ich2) 04h (82801b am ich2-m) function 4: 03h (both ich2 and ich2-m) bit description 7:3 reserved. 2:0 interrupt pin ?ro. the value of 03h in function 2 indicates that the ich2 will drive pirqd# as its interrupt line for usb controller 0 (ports 0 and 1). the value of 03h in function 4 indicates that the ich2 will drive pirqc# as its interrupt line for usb controller 1 (ports 2 and 3). however, in the ich2 implementation, when the usb controller 1 interrupt is generated pirq[h]# will go active, not pirq[c]#. bit description 7:0 serial bus release number ?ro. 10h = indicates that the usb controller is compliant with the usb specification release 1.0. usb controller registers 11-6 82801BA ich2 and 82801BAm ich2-m datasheet 11.1.15 usb_legkey?usb legacy keyboard/mouse control register (usb?d31:f2/f4) address offset: c0?c1 attribute: r/w, r/wc, ro default value: 2000h size: 16 bits bit description 15 smi caused by end of pass-through (smibyendps) ?r/wc. indicates if the event occurred. note that even if the corresponding enable bit is not set in bit 0, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software clears this bit by writing a 1 to the bit location. 14 reserved. 13 pci interrupt enable (usbpirqen) ?r/w. used to prevent the usb controller from generating an interrupt due to transactions on its ports. note that it will probably be configured to generate an smi using bit 4 of this register. default to 1 for compatibility with older usb software. 1 = enable 0 = disable 12 smi caused by usb interrupt (smibyusb) ?ro. indicates if the event occurred. note that even if the corresponding enable bit is not set in the bit 4, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software should clear the irq via the usb controller. writing a 1 to this bit will have no effect. 11 smi caused by port 64 write (trapby64w) ?r/wc. indicates if the event occurred. note that even if the corresponding enable bit is not set in bit 3, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software clears this bit by writing a 1 to the bit location. 10 smi caused by port 64 read (trapby64r) ?r/wc. indicates if the event occurred. note that even if the corresponding enable bit is not set in bit 2, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software clears this bit by writing a 1 to the bit location. 9 smi caused by port 60 write (trapby60w) ?r/wc. indicates if the event occurred. note that even if the corresponding enable bit is not set in bit 1, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software clears this bit by writing a 1 to the bit location. 8 smi caused by port 60 read (trapby60r) ?r/wc. indicates if the event occurred. note that even if the corresponding enable bit is not set in bit 0, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 1 = event occurred 0 = software clears this bit by writing a 1 to the bit location. 7 smi at end of pass-through enable (smiatendps) ?r/w. may need to cause smi at the end of a pass-through. can occur if an smi is generated in the middle of a pass through, and needs to be serviced later. 1 = enable 0 = disable 6 pass through state (pstate) ?ro. 1 = indicates that the state machine is in the middle of an a20gate pass-through sequence. 0 = if software needs to reset this bit, it should set bit 5 to 0. 5 a20gate pass-through enable (a20passen) ?r/w. 1 = allows a20gate sequence pass-through function. smi# will not be generated, even if the various enable bits are set. 0 = disable 82801BA ich2 and 82801BAm ich2-m datasheet 11-7 usb controller registers 11.1.16 usb_res?usb resume enable register (usb?d31:f2/f4) address offset: c4h attribute: r/w default value: 00h size: 8 bits 4 smi on usb irq enable (usbsmien) ?r/w. 1 = usb interrupt will cause an smi event. 0 = disable 3 smi on port 64 writes enable (64wen) ?r/w. 1 = a write to port 64h will cause an smi event. 0 = disable 2 smi on port 64 reads enable (64ren) ?r/w. 1 = a read to port 64h will cause an smi event. 0 = disable 1 smi on port 60 writes enable (60wen) ?r/w. 1 = a write to port 60h will cause an smi event. 0 = disable 0 smi on port 60 reads enable (60ren) ?r/w. 1 = a read to port 60h will cause an smi event. 0 = disable bit description bit description 7:2 reserved. 1 port1en ?r/w. enable the usb controller to respond to wakeup events on this port. for function 2 this applies to port 1; for function 4, this applies to port 3. 1 = the usb controller will monitor this port for remote wakeup and connect/disconnect events. 0 = the usb controller will not look at this port for a wakeup event. 0 port0en ?r/w. enable the usb controller to respond to wakeup events on this port. for function 2 this applies to port 0; for function 4, this applies to port 2. 1 = the usb controller will monitor this port for remote wakeup and connect/disconnect events. 0 = the usb controller will not look at this port for a wakeup event. usb controller registers 11-8 82801BA ich2 and 82801BAm ich2-m datasheet 11.2 usb i/o registers some of the read/write register bits that deal with changing the state of the usb hub ports function such that on read back they reflect the current state of the port, and not necessarily the state of the last write to the register. this allows the software to poll the state of the port and wait until it is in the proper state before proceeding. a host controller reset, global reset, or port reset will immediately terminate a transfer on the affected ports and disable the port. this affects the usbcmd register, bit [4] and the portsc registers, bits [12,6,2]. see individual bit descriptions for more detail. notes: 1. these registers are word writable only. byte writes to these registers have unpredictable effects. 11.2.1 usbcmd?usb command register i/o offset: base + (00?01h) attribute: r/w default value: 0000h size: 16 bits the command register indicates the command to be executed by the serial bus host controller. writing to the register causes a command to be executed. the table following the bit description provides additional information on the operation of the run/stop and debug bits. table 11-2. usb i/o registers offset mnemonic register default type 00?01h usbcmd usb command register 0000h r/w* 02?03h usbsts usb status register 0020h r/wc 04?05h usbintr usb interrupt enable 0000h r/w 06?07h frnum usb frame number 0000h r/w (see note 1) 08?0bh frbaseadd usb frame list base address undefined r/w 0ch sofmod usb start of frame modify 40h r/w 0d?0fh ? reserved 0 ro 10?11h portsc0 port 0 status/control 0080h r/wc (see note 1) 12?13h portsc1 port 1 status/control 0080h r/wc (see note 1) 14?17h ? reserved 0 ro 18h loopdata loop back test data 00h ro bit description 15:7 reserved. 8 loop back test mode ?r/w. 1 = ich2 is in loop back test mode. when both ports are connected together, a write to one port will be seen on the other port and the data will be stored in i/o offset 18h. 0 = disable loop back test mode. 7 max packet (maxp) ?r/w. this bit selects the maximum packet size that can be used for full speed bandwidth reclamation at the end of a frame. this value is used by the host controller to determine whether it should initiate another transaction based on the time remaining in the sof counter. use of reclamation packets larger than the programmed size will cause a babble error if executed during the critical window at frame end. the babble error results in the offending endpoint being stalled. software is responsible for ensuring that any packet which could be executed under bandwidth reclamation be within this size limit. 1 = 64 bytes 0 = 32 bytes 82801BA ich2 and 82801BAm ich2-m datasheet 11-9 usb controller registers 6 configure flag (cf) ?r/w. this bit has no effect on the hardware. it is provided only as a semaphore service for software. 1 = hcd software sets this bit as the last action in its process of configuring the host controller. 0 = indicates that software has not completed host controller configuration. 5 software debug (swdbg) ?r/w. the swdbg bit must only be manipulated when the controller is in the stopped state. this can be determined by checking the hchalted bit in the usbsts register. 1 = debug mode. in sw debug mode, the host controller clears the run/stop bit after the completion of each usb transaction. the next transaction is executed when software sets the run/stop bit back to 1. 0 = normal mode. 4 force global resume (fgr) ?r/w. 1 = host controller sends the global resume signal on the usb, and sets this bit to 1 when a resume event (connect, disconnect, or k-state) is detected while in global suspend mode. 0 = software resets this bit to 0 after 20 ms has elapsed to stop sending the global resume signal. at that time all usb devices should be ready for bus activity. the 1 to 0 transition causes the port to send a low speed eop signal. this bit will remain a 1 until the eop has completed. 3 enter global suspend mode (egsm) ?r/w. 1 = host controller enters the global suspend mode. no usb transactions occur during this time. the host controller is able to receive resume signals from usb and interrupt the system. software must ensure that the run/stop bit (bit 0) is cleared prior to setting this bit. 0 = software resets this bit to 0 to come out of global suspend mode. software writes this bit to 0 at the same time that force global resume (bit 4) is written to 0 or after writing bit 4 to 0. 2 global reset (greset) ?r/w. 1 = global reset. the host controller sends the global reset signal on the usb and then resets all its logic, including the internal hub registers. the hub registers are reset to their power on state. chip hardware reset has the same effect as global reset (bit 2), except that the host controller does not send the global reset on usb. 0 = this bit is reset by the software after a minimum of 10 ms has elapsed as specified in chapter 7 of the usb specification. 1 host controller reset (hcreset) ?r/w. the effects of hcreset on hub registers are slightly different from chip hardware reset and global usb reset. the hcreset affects bits [8,3:0] of the port status and control register (portsc) of each port. hcreset resets the state machines of the host controller including the connect/disconnect state machine (one for each port). when the connect/disconnect state machine is reset, the output that signals connect/disconnect are negated to 0, effectively signaling a disconnect, even if a device is attached to the port. this virtual disconnect causes the port to be disabled. this disconnect and disabling of the port causes bit 1 (connect status change) and bit 3 (port enable/disable change) of the portsc to get set. the disconnect also causes bit 8 of portsc to reset. about 64 bit times after hcreset goes to 0, the connect and low-speed detect will take place, and bits 0 and 8 of the portsc will change accordingly. 1 = reset. when this bit is set, the host controller module resets its internal timers, counters, state machines, etc. to their initial value. any transaction currently in progress on usb is immediately terminated. 0 = reset by the host controller when the reset process is complete. 0 run/stop (rs) ?r/w. when set to 1, the ich2 proceeds with execution of the schedule. the ich2 continues execution as long as this bit is set. when this bit is cleared, the ich2 completes the current transaction on the usb and then halts. the hc halted bit in the status register indicates when the host controller has finished the transaction and has entered the stopped state. the host controller clears this bit when the following fatal errors occur: consistency check failure, pci bus errors. 1 = run 0 = stop bit description usb controller registers 11-10 82801BA ich2 and 82801BAm ich2-m datasheet when the usb host controller is in software debug mode (usbcmd register bit 5=1), the single stepping software debug operation is as follows: to enter software debug mode: 1. hcd puts host controller in stop state by setting the run/stop bit to 0. 2. hcd puts host controller in debug mode by setting the swdbg bit to 1. 3. hcd sets up the correct command list and start of frame value for starting point in the frame list single step loop. 4. hcd sets run/stop bit to 1. 5. host controller executes next active td, sets run/stop bit to 0, and stops. 6. hcd reads the usbcmd register to check if the single step execution is completed (hchalted=1). 7. hcd checks results of td execution. go to step 4 to execute next td or step 8 to end software debug mode. 8. hcd ends software debug mode by setting swdbg bit to 0. 9. hcd sets up normal command list and frame list table. 10. hcd sets run/stop bit to 1 to resume normal schedule execution. in software debug mode, when the run/stop bit is set, the host controller starts. when a valid td is found, the run/stop bit is reset. when the td is finished, the hchalted bit in the usbsts register (bit 5) is set. the sw debug mode skips over inactive tds and only halts after an active td has been executed. when the last active td in a frame has been executed, the host controller waits until the next sof is sent and then fetches the first td of the next frame before halting. this hchalted bit can also be used outside of software debug mode to indicate when the host controller has detected the run/stop bit and has completed the current transaction. outside of the software debug mode, setting the run/stop bit to 0 always resets the sof counter so that when the run/stop bit is set the host controller starts over again from the frame list location pointed to by the frame list index (see frnum register description) rather than continuing where it stopped. table 11-3. run/stop, debug bit interaction swdbg (bit 5), run/stop (bit 0) operation swdbg (bit 5) run/stop (bit 0) description 00 if executing a command, the host controller completes the command and then stops. the 1.0 ms frame counter is reset and command list execution resumes from start of frame using the frame list pointer selected by the current value in the frnum register. (while run/stop=0, the frnum register can be reprogrammed). 01 execution of the command list resumes from start of frame using the frame list pointer selected by the current value in the frnum register. the host controller remains running until the run/stop bit is cleared (by software or hardware). 10 if executing a command, the host controller completes the command and then stops and the 1.0 ms frame counter is frozen at its current value. all status are preserved. the host controller begins execution of the command list from where it left off when the run/stop bit is set. 11 execution of the command list resumes from where the previous execution stopped. the run/stop bit is set to 0 by the host controller when a td is being fetched. this causes the host controller to stop again after the execution of the td (single step). when the host controller has completed execution, the hc halted bit in the status register is set. 82801BA ich2 and 82801BAm ich2-m datasheet 11-11 usb controller registers 11.2.2 usbsta?usb status register i/o offset: base + (02?03h) attribute: r/wc default value: 0020h size: 16 bits this register indicates pending interrupts and various states of the host controller. the status resulting from a transaction on the serial bus is not indicated in this register. software sets a bit to 0 in this register by writing a 1 to it. bit description 15:6 reserved. 5 hchalted ?r/wc. 1 = the host controller has stopped executing as a result of the run/stop bit being set to 0, either by software or by the host controller hardware (debug mode or an internal error). default. 0 = software resets this bit to 0 by writing a 1 to the bit position. 4 host controller process error ?r/wc. 1 = the host controller has detected a fatal error. this indicates that the host controller suffered a consistency check failure while processing a transfer descriptor. an example of a consistency check failure would be finding an illegal pid field while processing the packet header portion of the td. when this error occurs, the host controller clears the run/stop bit in the command register to prevent further schedule execution. a hardware interrupt is generated to the system. 0 = software resets this bit to 0 by writing a 1 to the bit position. 3 host system error ?r/wc. 1 = a serious error occurred during a host system access involving the host controller module. in a pci system, conditions that set this bit to 1 include pci parity error, pci master abort, and pci target abort. when this error occurs, the host controller clears the run/stop bit in the command register to prevent further execution of the scheduled tds. a hardware interrupt is generated to the system. 0 = software resets this bit to 0 by writing a 1 to the bit position. 2 resume detect (rsm_det) ?r/wc. 1 = the host controller received a ?resume? signal from a usb device. this is only valid if the host controller is in a global suspend state (bit 3 of command register = 1). 0 = software resets this bit to 0 by writing a 1 to the bit position. 1 usb error interrupt ?r/wc. 1 = completion of a usb transaction resulted in an error condition (e.g., error counter underflow). if the td on which the error interrupt occurred also had its ioc bit set, both this bit and bit 0 are set. 0 = software resets this bit to 0 by writing a 1 to the bit position. 0 usb interrupt (usbint) ?r/wc. 1 = the host controller sets this bit when the cause of an interrupt is a completion of a usb transaction whose transfer descriptor had its ioc bit set. also set when a short packet is detected (actual length field in td is less than maximum length field in td), and short packet detection is enabled in that td. 0 = software resets this bit to 0 by writing a 1 to the bit position. usb controller registers 11-12 82801BA ich2 and 82801BAm ich2-m datasheet 11.2.3 usbintr?interrupt enable register i/o offset: base + (04?05h) attribute: r/w default value: 0000h size: 16 bits this register enables and disables reporting of the corresponding interrupt to the software. when a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. fatal errors (host controller processor error-bit 4, usbsts register) cannot be disabled by the host controller. interrupt sources that are disabled in this register still appear in the status register to allow the software to poll for events. 11.2.4 frnum?frame number register i/o offset: base + (06?07h) attribute: r/w (writes must be word writes) default value: 0000h size: 16 bits bits [10:0] of this register contain the current frame number which is included in the frame sof packet. this register reflects the count value of the internal frame number counter. bits [9:0] are used to select a particular entry in the frame list during scheduled execution. this register is updated at the end of each frame time. this register must be written as a word. byte writes are not supported. this register cannot be written unless the host controller is in the stopped state as indicated by the hchalted bit (usbsts register). a write to this register while the run/stop bit is set (usbcmd register) is ignored. bit description 15:4 reserved. 3 short packet interrupt enable ?r/w. 1 = enabled. 0 = disabled. 2 interrupt on complete (ioc) enable ?r/w. 1 = enabled. 0 = disabled. 1 resume interrupt enable ?r/w. 1 = enabled. 0 = disabled. 0 time-out/crc interrupt enable ?r/w. 1 = enabled. 0 = disabled. bit description 15:11 reserved. 10:0 frame list current index/frame number ?r/w. provides the frame number in the sof frame. the value in this register increments at the end of each time frame (approximately every 1 ms). in addition, bits [9:0] are used for the frame list current index and correspond to memory address signals [11:2]. 82801BA ich2 and 82801BAm ich2-m datasheet 11-13 usb controller registers 11.2.5 frbaseadd?frame list base address i/o offset: base + (08?0bh) attribute: r/w default value: undefined size: 32 bits this 32-bit register contains the beginning address of the frame list in the system memory. hcd loads this register prior to starting the schedule execution by the host controller. when written, only the upper 20 bits are used. the lower 12 bits are written as zero (4-kb alignment). the contents of this register are combined with the frame number counter to enable the host controller to step through the frame list in sequence. the two least significant bits are always 00. this requires dword alignment for all list entries. this configuration supports 1024 frame list entries. 11.2.6 sofmod?start of frame modify register i/o offset: base + (0ch) attribute: r/w default value: 40h size: 8 bits this 1-byte register is used to modify the value used in the generation of sof timing on the usb. only the 7 least significant bits are used. when a new value is written into these 7 bits, the sof timing of the next frame will be adjusted. this feature can be used to adjust out any offset from the clock source that generates the clock that drives the sof counter. this register can also be used to maintain real time synchronization with the rest of the system so that all devices have the same sense of real time. using this register, the frame length can be adjusted across the full range required by the usb specification. its initial programmed value is system dependent based on the accuracy of hardware usb clock and is initialized by system bios. it may be reprogrammed by usb system software at any time. its value will take effect from the beginning of the next frame. this register is reset upon a host controller reset or global reset. software must maintain a copy of its value for reprogramming if necessary. bit description 31:12 base address ?r/w. these bits correspond to memory address signals [31:12], respectively. 11:0 reserved. bit description 7 reserved. 6:0 sof timing value ?r/w. guidelines for the modification of frame time are contained in chapter 7 of the usb specification. the sof cycle time (number of sof counter clock periods to generate a sof frame length) is equal to 11936 + value in this field. the default value is decimal 64 which gives a sof cycle time of 12000. for a 12 mhz sof counter clock input, this produces a 1 ms frame period. the following table indicates what sof timing value to program into this field for a certain frame period. frame length (# 12 mhz clocks) sof reg. value (decimal) (decimal) 11936 0 11937 1 .. .. 11999 63 12000 64 12001 65 .. .. 12062 126 12063 127 usb controller registers 11-14 82801BA ich2 and 82801BAm ich2-m datasheet 11.2.7 portsc[0,1]?port status and control register i/o offset: port 0/2: base + (10?11h) attribute: r/w (word writes only) port 1/3: base + (12?13h) default value: 0080h size: 16 bits note: for function 2, this applies to ich2 usb ports 0 and 1. for function 4, this applies to ich2 usb ports 2 and 3. after a power-up reset, global reset, or host controller reset, the initial conditions of a port are: no device connected, port disabled, and the bus line status is 00 (single-ended zero). bit description 15:13 reserved?ro. 12 suspend ?r/w . this bit should not be written to a 1 if global suspend is active (bit 3=1 in the usbcmd register). bit 2 and bit 12 of this register define the hub states as follows: bits [12,2] hub state x0 disable 01 enable 11 suspend when in suspend state, downstream propagation of data is blocked on this port, except for single- ended 0 resets (global reset and port reset). the blocking occurs at the end of the current transaction, if a transaction was in progress when this bit was written to 1. in the suspend state, the port is sensitive to resume detection. note that the bit status does not change until the port is suspended and that there may be a delay in suspending a port if there is a transaction currently in progress on the usb. 1 = port in suspend state. 0 = port not in suspend state. note: normally, if a transaction is in progress when this bit is set, the port will be suspended when the current transaction completes. however, in the case of a specific error condition (out transaction with babble), the ich2 may issue a start-of-frame, and then suspend the port. 11 overcurrent indicator ?r/wc. set by hardware 1 = overcurrent pin has gone from inactive to active on this port. 0 = software clears this bit by writing a 1 to the bit position. 10 overcurrent active ?ro. this bit is set and cleared by hardware. 1 = indicates that the overcurrent pin is active (low). 0 = indicates that the overcurrent pin is inactive (high). 9 port reset ?ro . 1 = port is in reset. when set, the port is disabled and sends the usb reset signaling. 0 = port is not in reset. 8 low speed device attached (ls) ?ro . writes have no effect. 1 = low speed device is attached to this port. 0 = full speed device is attached. 7 reserved?ro. always read as 1. 6 resume detect (rsm_det)? r/w. software sets this bit to a 1 to drive resume signaling. the host controller sets this bit to a 1 if a j-to-k transition is detected for at least 32 microseconds while the port is in the suspend state. the ich2 then reflects the k-state back onto the bus as long as the bit remains a 1 and the port is still in the suspend state (bit 12,2 are 11). writing a 0 (from 1) causes the port to send a low speed eop. this bit will remain a 1 until the eop has completed. 1 = resume detected/driven on port. 0 = no resume (k-state) detected/driven on port. 5:4 line status ?ro . these bits reflect the d+ (bit 4) and d- (bit 5) signals lines? logical levels. these bits are used for fault detect and recovery as well as for usb diagnostics. this field is updated at eof2 time (see chapter 11 of the usb specification). 82801BA ich2 and 82801BAm ich2-m datasheet 11-15 usb controller registers 3 port enable/disable change ?r/wc . for the root hub, this bit gets set only when a port is disabled due to disconnect on that port or due to the appropriate conditions existing at the eof2 point (see chapter 11 of the usb specification). 1 = port enabled/disabled status has changed. 0 = no change. software clears this bit by writing a 1 to the bit location. 2 port enabled/disabled (port_en)? r/w . ports can be enabled by host software only. ports can be disabled by either a fault condition (disconnect event or other fault condition) or by host software. note that the bit status does not change until the port state actually changes and that there may be a delay in disabling or enabling a port if there is a transaction currently in progress on the usb. 1 = enable. 0 = disable. 1 connect status change ?r/wc . indicates that a change has occurred in the port?s current connect status (see bit 0). the hub device sets this bit for any changes to the port device connect status, even if system software has not cleared a connect status change. if, for example, the insertion status changes twice before system software has cleared the changed condition, hub hardware will be setting? an already-set bit (i.e., the bit will remain set). however, the hub transfers the change bit only once when the host controller requests a data transfer to the status change endpoint. system software is responsible for determining state change history in such a case. 1 = change in current connect status. 0 = no change. software clears this bit by writing a 1 to the bit location. 0 current connect status ?ro . this value reflects the current state of the port, and may not correspond directly to the event that caused the connect status change bit (bit 1) to be set. 1 = device is present on port. 0 = no device is present. bit description usb controller registers 11-16 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank. 82801BA ich2 and 82801BAm ich2-m datasheet 12-1 smbus controller registers (d31:f3) smbus controller registers (d31:f3) 12 12.1 pci configuration registers (smbus?d31:f3) note: registers that are not shown should be treated as reserved (see section 6.2 for details). 12.1.1 vid?vendor identification register (smbus?d31:f3) address: 00?01h attributes: ro default value: 8086h size: 16 bits 12.1.2 did?device identification register (smbus?d31:f3) address: 02?03h attributes: ro default value: 2443h size: 16 bits table 12-1. pci configuration registers (smbus?d31:f3) offset mnemonic register name/function attribute 00?01h vid vendor id ro 02?03h did device id ro 04?05h cmd command register ro, r/w 06?07h sta device status ro, r/wc 08h rid revision id ro 09h pi programming interface ro 0ah scc sub class code ro 0bh bcc base class code ro 20?23h smb_base smbus base address register r/w 2c?2dh svid subsystem vendor id ro 2e?2fh sid subsystem id ro 3ch intr_ln interrupt line r/w 3dh intr_pn interrupt pin ro 40h hostc host configuration r/w bit description 15:0 vendor id value? ro. this is a 16 bit value assigned to intel bit description 15:0 device id value? ro. smbus controller registers (d31:f3) 12-2 82801BA ich2 and 82801BAm ich2-m datasheet 12.1.3 cmd?command register (smbus?d31:f3) address: 04?05h attributes: ro, r/w default value: 0000h size: 16 bits 12.1.4 sta?device status register (smbus?d31:f3) address: 06?07h attributes: ro, r/wc default value: 0280h size: 16 bits bit description 15:10 reserved. 9 fast back to back enable (fbe)?ro. reserved as 0. 8 serr# enable (serren)?ro. reserved as 0. 7 wait cycle control (wcc)?ro. reserved as 0. 6 parity error response (per)?ro. reserved as 0. 5 vga palette snoop (vps)?ro. reserved as 0. 4 postable memory write enable (pmwe)?ro. reserved as 0. 3 special cycle enable (sce)?ro. reserved as 0. 2 bus master enable (bme)?ro. reserved as 0. 1 memory space enable (mse)?ro. reserved as 0. 0 i/o space enable (iose)? r/w. 0 = disable. 1 = enables access to the sm bus i/o space registers as defined by the base address register. bit description 15 detected parity error (dpe)?ro. reserved as 0. 14 signaled system error (sse)?ro. reserved as 0. 13 received master abort (rma)?ro. reserved as 0. 12 received target abort (rta)?ro. reserved as 0. 11 signaled target-abort status (sta) ?r/wc. 1 = function is targeted with a transaction that the ich2 terminates with a target abort. 0 = software resets sta to 0 by writing a 1 to this bit location. 10:9 devsel# timing status (devt) ?ro. this 2-bit field defines the timing for devsel# assertion for positive decode. 01 = medium timing. 8 data parity error detected?ro. reserved as 0. 7 fast back-to-back capable?ro. reserved as 1. 6 user definable features (udf)?ro. reserved as 0. 5 66 mhz capable?ro. reserved as 0. 4:0 reserved. 82801BA ich2 and 82801BAm ich2-m datasheet 12-3 smbus controller registers (d31:f3) 12.1.5 rid?revision id register ( smbus?d31:f3 ) offset address: 08h attribute: ro default value: see bit description size: 8 bits 12.1.6 pi?programming interface ( smbus?d31:f3 ) address offset: 09h attribute: ro default value: 80h size: 8 bits 12.1.7 scc?sub class code register (smbus?d31:f3) address offset: 0ah attributes: ro default value: 05h size: 8 bits 12.1.8 bcc?base class code register (smbus?d31:f3) address offset: 0bh attributes: ro default value: 0ch size: 8 bits bit description 7:0 revision identification number. 8-bit value that indicates the revision number for the smbus controller. refer to the specification update for the value of the revision id register bit description 7:0 programming interface value? ro. 80h = the 1b in bit 7 indicates that this ide controller is capable of bus master operation. bit description 7:0 sub class code ?ro. 05h = sm bus serial controller bit description 7:0 base class code ?ro. 0ch = serial controller. smbus controller registers (d31:f3) 12-4 82801BA ich2 and 82801BAm ich2-m datasheet 12.1.9 smb_base?smbus base address register (smbus?d31:f3) address offset: 20?23h attribute: r/w default value: 00000001h size: 32-bits 12.1.10 svid?subsystem vendor id (smbus?d31:f2/f4) address offset: 2ch?2dh attribute: ro default value: 00h size: 16 bits lockable: no power well: core 12.1.11 sid?subsystem id (smbus?d31:f2/f4) address offset: 2eh?2fh attribute: ro default value: 00h size: 16 bits lockable: no power well: core 12.1.12 intr_ln?interrupt line register (smbus?d31:f3) address offset: 3ch attributes: r/w default value: 00h size: 8 bits bit description 31:16 reserved. 15:4 base address? r/w. provides the 16-bit system i/o base address for the ich2 smb logic. 3:1 reserved. 0 io space indicator ?ro. this read-only bit is always 1, indicating that the smb logic is i/o mapped. bit description 15:0 subsystem vendor id (svid)? ro. the svid register, in combination with the subsystem id (sid) register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide_svid register. bit description 15:0 subsystem id (sid)? r/write-once. the sid register, in combination with the svid register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide_sid register. bit description 7:0 interrupt line? r/w. this data is not used by the ich2. it is to communicate to software the interrupt line that the interrupt pin is connected to pirqb#. 82801BA ich2 and 82801BAm ich2-m datasheet 12-5 smbus controller registers (d31:f3) 12.1.13 intr_pn?interrupt pin register (smbus?d31:f3) address offset: 3dh attributes: ro default value: 02h size: 8 bits 12.1.14 hostc?host configuration register (smbus?d31:f3) address offset: 40h attribute: r/w default value: 00h size: 8 bits bit description 7:0 interrupt pin? ro. 02h = indicates that the ich2 smbus controller will drive pirqb# as its interrupt line. bit description 7:3 reserved. 2 i 2 c enable (i2c_en)? r/w. 0 = smbus behavior. 1 = the ich2 is enabled to communicate with i 2 c devices. this will change the formatting of some commands. 1 smbus to smi enable (smb_smi_en)? r/w. 0 = smbus interrupts will not generate an smi#. 1 = any source of an smb interrupt will instead be routed to generate an smi#. this bit will only take effect if the intren bit is set in i/o space.this bit needs to be set for smbalert# to be enabled. 0 smbus host enable (hst_en) ?r/w. 0 = disable the smbus host controller. 1 = enable. the smb host controller interface is enabled to execute commands. the intren bit needs to be enabled for the smb host controller to interrupt or smi#. note that the smb host controller will not respond to any new requests until all interrupt requests have been serviced. smbus controller registers (d31:f3) 12-6 82801BA ich2 and 82801BAm ich2-m datasheet 12.2 smbus i/o registers table 12-2. smb i/o registers offset mnemonic register name/function default access 00h hst_sts host status 00h r/w 02h hst_cnt host control 00h r/w 03h hst_cmd host command 00h r/w 04h xmit_slva transmit slave address 00h r/w 05h hst_d0 host data 0 00h r/w 06h hst_d1 host data 1 00h r/w 07h block_db block data byte 00h r/w 08h ? reserved 00h ro 09h rcv_slva receive slave address 44h r/w 0ah slv_data slave data 0000h r/w 0bh?0dh ? reserved 00h ro 0eh smlink_pin_ctl smlink pin control see register description r/w 0fh smbus_pin_ctl smbus pin control see register description r/w 82801BA ich2 and 82801BAm ich2-m datasheet 12-7 smbus controller registers (d31:f3) 12.2.1 hst_sts?host status register register offset: 00h attribute: r/wc default value: 00h size: 8-bits all status bits are set by hardware and cleared by the software writing a one to the particular bit position. writing a zero to any bit position has no effect. bit description 7 byte done status (byte_done_sta)? r/wc. 1 = the ich2 has received a byte (for block read commands) or if it has completed transmission of a byte (for block write commands). this bit will be set even on the last byte of the transfer. it will not be set when transmission is due to the alert on lan* heartbeat. 0 = cleared by writing a 1 to the bit position. 6 in use status (inuse_sta)? r/wc (special). this bit is used as semaphore among various independent software threads that may need to use the ich2?s smbus logic and has no other effect on hardware. 0 = after a full pci reset, a read to this bit returns a 0. 1 = after the first read, subsequent reads will return a 1. a write of a 1 to this bit will reset the next read value to 0. writing a 0 to this bit has no effect. software can poll this bit until it reads a 0, and will then own the usage of the host controller. 5 smbus alert status (smbalert_sta)? r/wc. 0 = interrupt or smi# was not generated by smbalert#. 1 = the source of the interrupt or smi# was the smbalert# signal. this bit is only cleared by software writing a 1 to the bit position or by rsmrst# going low. if the signal is programmed as a gpio, then this bit will never be set. 4 interrupt/smi# was failed bus transaction (failed)? r/wc. 1 = the source of the interrupt or smi# was a failed bus transaction. this bit is set in response to the kill bit being set to terminate the host transaction. 0 = cleared by writing a 1 to the bit position. 3 bus error (bus_err) ?r/wc. 1 = the source of the interrupt of smi# was a transaction collision. 0 = cleared by writing a 1 to the bit position. 2 device error (dev_err) ?r/wc. 1 = the source of the interrupt or smi# was due to one of the following: ? illegal command field, ? unclaimed cycle (host initiated), ? host device time-out error.] 0 = software resets this bit by writing a 1 to this location. the ich2 will then deassert the interrupt or smi#. 1 interrupt/smi# was successful completion (intr)? r/wc (special). this bit can only be set by termination of a command. intr is not dependent on the intren bit of the host controller register (offset 02h); it is only dependent on the termination of the command. if the intren bit is not set, the intr bit will be set, although the interrupt will not be generated. software can poll the intr bit in this non-interrupt case. 1 = the source of the interrupt or smi# was the successful completion of its last command. 0 = software resets this bit by writing 1 to this location. the ich2 then deasserts the interrupt or smi#. 0 host busy (host_busy)? ro. 1 = indicates that the ich2 is running a command from the host interface. no smb registers should be accessed while this bit is set, except the block data byte register. the block data byte register can be accessed when this bit is set only when the smb_cmd bits in the host control register are programmed for block command or i 2 c read command. this is necessary in order to check the byte_done_sts bit. 0 = cleared by the ich2 when the current transaction is completed. smbus controller registers (d31:f3) 12-8 82801BA ich2 and 82801BAm ich2-m datasheet 12.2.2 hst_cnt?host control register register offset: 02h attribute: r/w default value: 00h size: 8-bits bit description 7 reserved. 6 start? wo. 1 = writing a 1 to this bit initiates the command described in the smb_cmd field. all registers should be setup prior to writing a 1 to this bit position. 0 = this bit will always return 0 on reads. the host_busy bit in the host status register (offset 00h) can be used to identify when the ich2 has finished the command. 5 last byte? wo. this bit is used for block read commands. 1 = software sets this bit to indicate that the next byte will be the last byte to be received for the block. this causes the ich2 to send a nack (instead of an ack) after receiving the last byte. 4:2 smbus command (smb_cmd)? r/w. the bit encoding below indicates which command the ich2 is to perform. if enabled, the ich2 generates an interrupt or smi# when the command has completed. if the value is for a non-supported or reserved command, the ich2 sets the device error (dev_err) status bit and generates an interrupt when the start bit is set. the ich2 performs no command and does not operate until dev_err is cleared. 000 = quick: the slave address and read/write value (bit 0) are stored in the transmit slave address register. 001 = byte: this command uses the transmit slave address and command registers. bit 0 of the slave address register determines if this is a read or write command. 010 = byte data: this command uses the transmit slave address, command, and data0 registers. bit 0 of the slave address register determines if this is a read or write command. if it is a read, the data0 register will contain the read data. 011 = word data: this command uses the transmit slave address, command, data0 and data1 registers. bit 0 of the slave address register determines if this is a read or write command. if it is a read, after the command completes, the data0 and data1 registers will contain the read data. 100 = process call: this command uses the transmit slave address, command, data0 and data1 registers. bit 0 of the slave address register determines if this is a read or write command. after the command completes, the data0 and data1 registers will contain the read data. 101 = block: this command uses the transmit slave address, command, data0 registers, and the block data byte register. for block write, the count is stored in the data0 register and indicates how many bytes of data will be transferred. for block reads, the count is received and stored in the data0 register. bit 0 of the slave address register selects if this is a read or write command. for writes, data is retrieved from the first n (where n is equal to the specified count) addresses of the sram array. for reads, the data is stored in the block data byte register. 110 = i 2 c read: this command uses the transmit slave address, command, data0, data1 registers, and the block data byte register. the read data is stored in the block data byte register. the ich2 will continue reading data until the nak is received. 111 = reserved 1 kill? r/w. 1 = when set, kills the current host transaction taking place, sets the failed status bit, and asserts the interrupt (or smi#). this bit, once set, must be cleared by software to allow the smbus host controller to function normally. 0 = normal smbus host controller functionality. 0 intren? r/w. 1 = enable the generation of an interrupt or smi# upon the completion of the command. 0 = disable. 82801BA ich2 and 82801BAm ich2-m datasheet 12-9 smbus controller registers (d31:f3) 12.2.3 hst_cmd?host command register register offset: 03h attribute: r/w default value: 00h size: 8 bits 12.2.4 xmit_slva?transmit slave address register register offset: 04h attribute: r/w default value: 00h size: 8 bits this register is transmitted by the host controller in the slave address field of the smbus protocol. 12.2.5 hst_d0?data 0 register register offset: 05h attribute: r/w default value: 00h size: 8 bits 12.2.6 hst_d1?data 1 register register offset: 06h attribute: r/w default value: 00h size: 8 bits bit description 7:0 host command ?r/w. this eight bit field is transmitted by the host controller in the command field of the smbus protocol during the execution of any command. bit description 7:1 address? r/w. 7-bit address of the targeted slave. 0 read/write select? r/w. direction of the host transfer. 0 = write 1 = read bit description 7:0 data0/count? r/w. this field contains the eight bit data sent in the data0 field of the smbus protocol. for block write commands, this register reflects the number of bytes to transfer. this register should be programmed to a value between 1 and 32 for block counts. a count of 0 or a count above 32 will result in unpredictable behavior. the host controller does not check or log illegal block counts. bit description 7:0 data1? r/w. this eight bit register is transmitted in the data1 field of the smbus protocol during the execution of any command. smbus controller registers (d31:f3) 12-10 82801BA ich2 and 82801BAm ich2-m datasheet 12.2.7 block_db?block data byte register register offset: 07h attribute: r/w default value: 00h size: 8 bits 12.2.8 rcv_slva?receive slave address register register offset: 09h attribute: r/w default value: 44h size: 8 bits lockable: no power well: resume 12.2.9 slv_data?receive slave data register register offset: 0ah attribute: ro default value: 00h size: 16 bits lockable: no power well: resume this register contains the 16-bit data value written by the external smbus master. the cpu can then read the value from this register. this register is reset by rsmrst#, but not pcirst#. bit description 7:0 block data byte? r/w. for block writes, software writes the first byte to this register as part of the setup for this command. after the ich2 has sent the address, command, and byte count fields, it will send the byte in the block data byte register. after the byte has been sent, the ich2 sets the byte_done_sts bit in the host status register. if there are more bytes to send, the software then writes in the next byte to the block data byte register and software also clears the byte_done_sts bit. the ich2 then sends the next byte. during the time from when a byte has been transmitted to when the next byte has been loaded, the ich2 inserts wait-states on the smbus/i 2 c. a similar process will be used for block reads. after receiving the byte count (which goes in the data 0 register), the first ?data byte? goes in the block data byte register and the ich2 generates an smi# or interrupt (depending on configuration). the interrupt or smi# handler then reads the byte and clears the byte_done_sts bit. this frees room for the next byte. during the time from when a byte is read to when the byte_done_sts bit is cleared, the ich2 inserts wait-states on the smbus/i 2 c. bit description 7 reserved 6:0 slave_addr? r/w. this field is the slave address that the ich2 decodes for read and write cycles. the default is not 0 so the smbus slave interface can respond even before the processor comes up (or if the processor is dead). this register is cleared by rsmrst#, but not by pcirst#. bit description 15:8 data_msg1: data message byte 1 ? ro. see section 5.17.5 for a discussion of this field. 7:0 data_msg0: data message byte 0 ? ro. see section 5.17.5 for a discussion of this field. 82801BA ich2 and 82801BAm ich2-m datasheet 12-11 smbus controller registers (d31:f3) 12.2.10 smlink_pin_ctl?smlink pin control register register offset: 0eh attribute: read/write default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 12.2.11 smbus_pin_ctl?smbus pin control register register offset: 0fh attribute: read/write default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:3 reserved 2 smlink clock pin control (smlink_clk_ctl)? r/w. 1 = no functional impact on the smlink[0] pin. (default) 0 = ich2 will drive the smlink[0] pin low, independent of the what the other smlink logic would otherwise indicate for the smlink[0] pin. 1 smlink[1] pin current status (smlink[1]_cur_sta)? ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smlink[1] pin. this allows software to read the current state of the pin. 1 = smlink[1] pin is high 0 = smlink[1] pin is low 0 smlink[0] pin current status (smlink[0]_cur_sta)? ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smlink[0] pin. this allows software to read the current state of the pin. 1 = smlink[0] pin is high 0 = smlink[0] pin is low bit description 7:3 reserved 2 smbclk pin control (smbclk_ctl) ?r/w. 1 = no functional impact on the smbclk pin. (default) 0 = ich2 drives the smbclk pin low, independent of the what the other smb logic would otherwise indicate for the smbclk pin. 1 smbdata pin current status (smbdata_cur_sta) ?ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smbdata pin. this allows software to read the current state of the pin. 1 = smbdata pin is high 0 = smbdata pin is low 0 smbclk pin current status (smbclk_cur_sta) ?ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smbclk pin. this allows software to read the current state of the pin. 1 = smbclk pin is high 0 = smbclk pin is low smbus controller registers (d31:f3) 12-12 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank. 82801BA ich2 and 82801BAm ich2-m datasheet 13-1 ac?97 audio controller registers (d31:f5) ac?97 audio controller registers (d31:f5) 13 13.1 ac?97 audio pci configuration space (d31:f5) note: registers that are not shown should be treated as reserved (see section 6.2 for details). note: refer to the specification update for the value of the revision id register 13.1.1 vid?vendor identification register (audio?d31:f5) offset: 01h-00h attribute: ro default value: 8086h size: 16 bits lockable: no power well: core table 13-1. pci configuration map (audio?d31:f5) offset mnemonic register default access 00h?01h vid vendor identification 8086h ro 02h?03h did device identification 2445h ro 04h?05h pcicmd pci command 0000 r/w 06h?07h pcists pci device status 0280h r/wc 08h rid revision identification see note ro 09h pi programming interface 00 ro 0ah scc sub class code 01h ro 0bh bcc base class code 04h ro 0eh hedt header type 00 ro 10h?13h nambar native audio mixer base address 00000001h r/w 14h?17h nabmbar native audio bus mastering base address 00000001h r/w 18h?2bh ? reserved 00h ro 2ch?2dh svid subsystem vendor id 0000h write-once 2eh?2fh sid subsystem id 0000h write-once 30h?3bh ? reserved ? ? 3ch intr_ln interrupt line 00h r/w 3dh intr_pn interrupt pin 02h ro 3eh?ffh ? reserved ? ? bit description 15:0 vendor id value. this is a 16 bit value assigned to intel ac?97 audio controller registers (d31:f5) 13-2 82801BA ich2 and 82801BAm ich2-m datasheet 13.1.2 did?device identification register (audio?d31:f5) offset: 03h?02h attribute: ro default value: 2445h size: 16 bits lockable: no power well: core 13.1.3 pcicmd?pci command register (audio?d31:f5) address offset: 05h?04h attribute: r/w default value: 0000h size: 16 bits lockable: no power well: core pcicmd is a 16-bit control register. refer to the pci 2.1 specification for complete details on each bit. bit description 15:0 device id value. bit description 15:10 reserved. read as 0s. 9 fast back to back enable (fbe). not implemented. hardwired to 0. 8 serr# enable (sen). not implemented. hardwired to 0. 7 wait cycle control (wcc). not implemented. hardwired to 0. 6 parity error response (per). not implemented. hardwired to 0. 5 vga palette snoop (vps). not implemented. hardwired to 0. 4 memory write and invalidate enable (mwi). not implemented. hardwired to 0. 3 special cycle enable (sce). not implemented. hardwired to 0. 2 bus master enable (bme) ?r/w. controls standard pci bus mastering capabilities. 0 = disable. 1 = enable 1 memory space (ms). hardwired to 0, ac '97 does not respond to memory accesses 0 ios (i/o space) ?r/w. this bit controls access to the ac?97 audio controller i/o space registers. 0 = disable (default). 1 = enable access to i/o space. the native pci mode base address register should be programmed prior to setting this bit. 82801BA ich2 and 82801BAm ich2-m datasheet 13-3 ac?97 audio controller registers (d31:f5) 13.1.4 pcists?pci device status register (audio?d31:f5) offset: 07h?06h attribute: r/wc default value 0280h size: 16 bits lockable: no power well: core pcista is a 16-bit status register. refer to the pci 2.1 specification for complete details on each bit. 13.1.5 rid?revision identification register (audio?d31:f5) offset: 08h attribute: ro default value: see bit description size: 8 bits lockable: no power well: core 13.1.6 pi?programming interface register (audio?d31:f5) offset: 09h attribute: ro default value: 00h size: 8 bits lockable: no power well: core bit description 15 detected parity error (dpe). not implemented. hardwired to 0. 14 serr# status (serrs). not implemented. hardwired to 0. 13 master-abort status (mas) ?r/wc. 1 = bus master ac '97 2.1 interface function, as a master, generates a master abort. 0 = software clears this bit by writing a 1 to the bit position. 12 reserved. will always read as 0. 11 signaled target-abort status (sta). not implemented. hardwired to 0. 10:9 devsel# timing status (devt)? ro. this 2-bit field reflects the ich2's devsel# timing when performing a positive decode. 01b = medium timing. 8 data parity detected (dpd). not implemented. hardwired to 0. 7 fast back to back capable (fbc). hardwired to 1. this bit indicates that the ich2 as a target is capable of fast back-to-back transactions. 6 udf supported. not implemented. hardwired to 0. 5 66 mhz capable. hardwired to 0. 4:0 reserved. read as 0's. bit description 7:0 revision id value? ro. refer to the ich2 / ich2-m specification update for the value of the revision id register bit description 7:0 programming interface? ro. ac?97 audio controller registers (d31:f5) 13-4 82801BA ich2 and 82801BAm ich2-m datasheet 13.1.7 scc?sub class code register (audio?d31:f5) address offset: 0ah attribute: ro default value: 01h size: 8 bits lockable: no power well: core 13.1.8 bcc?base class code register (audio?d31:f5) address offset: 0bh attribute: ro default value: 04h size: 8 bits lockable: no power well: core 13.1.9 hedt?header type register (audio?d31:f5) address offset: 0eh attribute: ro default value: 00h size: 8 bits lockable: no power well: core bit description 7:0 sub class code? ro. 01h = audio device bit description 7:0 base class code? ro. 04h = multimedia device bit description 7:0 header type value. hardwired to 00h. 82801BA ich2 and 82801BAm ich2-m datasheet 13-5 ac?97 audio controller registers (d31:f5) 13.1.10 nambar?native audio mixer base address register (audio?d31:f5) address offset: 10h?13h attribute: r/w default value: 00000001h size: 32 bits lockable: no power well: core the native pci mode audio function uses pci base address register #1 to request a contiguous block of i/o space that is to be used for the native audio mixer software interface. the mixer requires 256 bytes of i/o space. native audio mixer and modem codec i/o registers are located from 00h to 7fh and reside in the codec. access to these registers will be decoded by the ac '97 controller and forwarded over the ac-link to the codec. the codec will then respond with the register value. in the case of the split codec implementation, accesses to the different codecs are differentiated by the controller by using address offsets 00h?7fh for the primary codec and address offsets 80h?feh for the secondary codec. for a description of these i/o registers, refer to the ac?97 specification. 13.1.11 nabmbar?native audio bus mastering base address register (audio?d31:f5) address offset: 14h?17h attribute: r/w default value: 00000001h size: 32 bits lockable: no power well: core the native pci mode audio function uses pci base address register #1 to request a contiguous block of i/o space that is to be used for the native mode audio software interface. bit description 31:16 hardwired to 0s 15:8 base address? r/w. these bits are used in the i/o space decode of the native audio mixer interface registers. the number of upper bits that a device actually implements depends on how much of the address space the device will respond to. for the ac ?97 mixer, the upper 16 bits are hardwired to 0, while bits 15:8 are programmable. this configuration yields a maximum i/o block size of 256 bytes for this base address. note: this address must align to a 256-byte boundary. 7:1 reserved. read as 0s. 0 resource type indicator (rte)? ro. hardwired to 1 indicating a request for i/o space. bit description 31:16 hardwired to 0s 15:6 base address? r/w. these bits are used in the i/o space decode of the native audio bus mastering interface registers. the number of upper bits that a device actually implements depends on how much of the address space the device will respond to. for ac '97 bus mastering, the upper 16 bits are hardwired to 0, while bits 15:6 are programmable. this configuration yields a maximum i/o block size of 64 bytes for this base address. note: this address must align to a 64-byte boundary. 5:1 reserved. read as 0s. 0 resource type indicator (rte)? ro. this bit is set to 1 indicating a request for i/o space. ac?97 audio controller registers (d31:f5) 13-6 82801BA ich2 and 82801BAm ich2-m datasheet 13.1.12 svid?subsystem vendor id register (audio?d31:f5) address offset: 2dh?2ch attribute: read/write-once default value: 0000h size: 16 bits lockable: no power well: core the svid register, in combination with the subsystem id register, enable the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subsequent writes will have no effect. 13.1.13 sid?subsystem id register (audio?d31:f5) address offset: 2fh?2eh attribute: read/write-once default value: 0000h size: 16 bits lockable: no power well: core the sid register, in combination with the subsystem vendor id register make it possible for the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subsequent writes will have no effect. 13.1.14 intr_ln?interrupt line register (audio?d31:f5) address offset: 3ch attribute: r/w default value: 00h size: 8 bits lockable: no power well: core this register indicates which pci interrupt line is used for the ac?97 module interrupt. bit description 15:0 subsystem vendor id value? r/write-once. bit description 15:0 subsystem id value? r/write-once. bit description 7:0 interrupt line? r/w. this data is not used by the ich2. it is used to communicate to software the interrupt line that the interrupt pin is connected to. 82801BA ich2 and 82801BAm ich2-m datasheet 13-7 ac?97 audio controller registers (d31:f5) 13.1.15 intr_pn?interrupt pin register (audio?d31:f5) address offset: 3dh attribute: ro default value: 02h size: 8 bits lockable: no power well: core this register indicates which pci interrupt pin is used for the ac '97 module interrupt. the ac '97 interrupt is internally or?ed to the interrupt controller with the pirqb# signal. 13.2 ac?97 audio i/o space (d31:f5) the ac?97 i/o space includes native audio bus master registers and native mixer registers. table 13-2 shows the register addresses for the audio mixer registers. bit description 7:3 reserved. 2:0 ac '97 interrupt routing? ro. hardwired to 010b to select pirqb#. table 13-2. ich2 audio mixer register configuration primary offset secondary offset nambar exposed registers (d31:f5) 00h 80h reset 02h 82h master volume mute 04h 84h headphone volume mute 06h 86h master volume mono mute 08h 88h master tone (r & l) 0ah 8ah pc_beep volume mute 0ch 8ch phone volume mute 0eh 8eh mic volume mute 10h 90h line in volume mute 12h 92h cd volume mute 14h 94h video volume mute 16h 96h aux volume mute 18h 98h pcm out volume mute 1ah 9ah record select 1ch 9ch record gain mute 1eh 9eh record gain mic mute 20h a0h general purpose 22h a2h 3d control 24h a4h ac?97 reserved 26h a6h powerdown ctrl/stat 28h a8h extended audio 2ah aah extended audio ctrl/stat ac?97 audio controller registers (d31:f5) 13-8 82801BA ich2 and 82801BAm ich2-m datasheet note: 1. registers in bold are multiplexed between audio and modem functions 2. software should not try to access reserved registers the bus master registers are located from offset + 00h to offset + 51h and reside in the ac ?97 controller. accesses to these registers do not cause the cycle to be forwarded over the ac-link to the codec. in the case of the split codec implementation accesses to the different codecs are differentiated by the controller by using address offsets 00h?7fh for the primary codec and address offsets 80h?feh for the secondary codec. the global control (glob_cnt) and global status (glob_sta) registers are aliased to the same global registers in the audio and modem i/o space. therefore a read/write to these registers in either audio or modem i/o space affects the same physical register. bus mastering registers exist in i/o space and reside in the ac ?97 controller. the three channels (pcm in, pcm out, and mic in) each have their own set of bus mastering registers. the following register descriptions apply to all three channels. the register definition section titles use a generic ?x_? in front of the register to indicate that the register applies to all three channels. the naming prefix convention used in table 13-3 and in the register description i/o address is as follows: ? pi = pcm in channel ? po = pcm out channel ? mc = mic in channel. 2ch ach pcm front dac rate 2eh aeh pcm surround dac rate 30h b0h pcm lfe dac rate 32h b2h pcm lr adc rate 34h b4h mic adc rate 36h b6h 6ch vol: c, lfe mute 38h b8h 6ch vol: l, r surround mute 3ah:56h bah?f6h intel reserved 58h 1 vendor reserved 7ah 1 vendor reserved 7ch 1 vendor id1 7eh 1 vendor id2 table 13-2. ich2 audio mixer register configuration (continued) primary offset secondary offset nambar exposed registers (d31:f5) 82801BA ich2 and 82801BAm ich2-m datasheet 13-9 ac?97 audio controller registers (d31:f5) 13.2.1 x _bdbar?buffer descriptor base address register i/o address: nabmbar + 00h (pibdbar), attribute: r/w (dword access only) nabmbar + 10h (pobdbar), nabmbar + 20h (mcbdbar) default value: 00000000h size: 32 bits lockable: no power well: core this register can be accessed only as a dword (32 bits). table 13-3. native audio bus master control registers offset mnemonic name default access 00h pi_bdbar pcm in buffer descriptor list base address register 00000000h r/w 04h pi_civ pcm in current index value 00h ro 05h pi_lvi pcm in last valid index 00h r/w 06h pi_sr pcm in status register 0001h r/w 08h pi_picb pcm in position in current buffer 0000h ro 0ah pi_piv pcm in prefetched index value 00h ro 0bh pi_cr pcm in control register 00h r/w 10h po_bdbar pcm out buffer descriptor list base address register 00000000h r/w 14h po_civ pcm out current index value 00h ro 15h po_lvi pcm out last valid index 00h r/w 16h po_sr pcm out status register 0001h r/w 18h po_picb pcm out position in current buffer 0000h ro 1ah po_piv pcm out prefetched index value 00h ro 1bh po_cr pcm out control register 00h r/w 20h mc_bdbar mic. in buffer descriptor list base address register 00000000h r/w 24h pm_civ mic. in current index value 00h ro 25h mc_lvi mic. in last valid index 00h r/w 26h mc_sr mic. in status register 0001h r/w 28h mc_picb mic in position in current buffer 0000h ro 2ah mc_piv mic. in prefetched index value 00h ro 2bh mc_cr mic. in control register 00h r/w 2ch glob_cnt global control 00000000h r/w 30h glob_sta global status 00000000h ro 34h acc_sema codec write semaphore register 00h r/w bit description 31:3 buffer descriptor base address[31:3]? r/w. these bits represent address bits 31:3. the data should be aligned on 8 byte boundaries. each buffer descriptor is 8 bytes long and the list can contain a maximum of 32 entries. 2:0 hardwired to 0. ac?97 audio controller registers (d31:f5) 13-10 82801BA ich2 and 82801BAm ich2-m datasheet 13.2.2 x _civ?current index value register i/o address: nabmbar + 04h (piciv), attribute: ro nabmbar + 14h (pociv), nabmbar + 24h (mcciv) default value: 00h size: 8 bits lockable: no power well: core software can read the registers at offsets 04h, 05h and 06h simultaneously by performing a single 32 bit read from address offset 04h. software can also read this register individually by doing a single 8 bit read to offset 04h. 13.2.3 x _lvi?last valid index register i/o address: nabmbar + 05h (pilvi), attribute: r/w nabmbar + 15h (polvi), nabmbar + 25h (mclvi) default value: 00h size: 8 bits lockable: no power well: core software can read the registers at offsets 04h, 05h and 06h simultaneously by performing a single 32 bit read from address offset 04h. software can also read this register individually by doing a single 8 bit read to offset 05h. bit description 7:5 hardwired to 0 4:0 current index value[4:0]? ro. these bits represent which buffer descriptor within the list of 32 descriptors is currently being processed. as each descriptor is processed, this value is incremented. the value rolls over after it reaches 31. bit description 7:5 hardwired to 0. 4:0 last valid index[4:0]? r/w. this value represents the last valid descriptor in the list. this value is updated by the software each time it prepares a new buffer and adds it to the list. 82801BA ich2 and 82801BAm ich2-m datasheet 13-11 ac?97 audio controller registers (d31:f5) 13.2.4 x _sr?status register i/o address: nabmbar + 06h (pisr), attribute: r/wc, ro (word access only) nabmbar + 16h (posr), nabmbar + 26h (mcsr) default value: 0001h size: 16 bits lockable: no power well: core this register can be accessed only as a word (16 bits). software can read the above 3 registers simultaneously by scheduling a single 32 bit read from address offset 04h. software can also read this individual register by performing a 16 bit read from 06h. bit description 15:5 reserved. 4 fifo error (fifoe)? r/wc. 1 = fifo error occurs. 0 = cleared by writing a 1 to this bit position. pisr register: fifo error indicates a fifo overrun. the fifo pointers do not increment, the incoming data is not written into the fifo, thus is lost. posr register: fifo error indicates a fifo underrun. the sample transmitted in this case should be the last valid sample. the ich2 will set the fifoe bit if the under-run or overrun occurs when there are more valid buffers to process. 3 buffer completion interrupt status (bcis)? r/wc. 1 = set by the hardware after the last sample of a buffer has been processed, and if the interrupt on completion (ioc) bit is set in the command byte of the buffer descriptor. it remains active until cleared by software. 0 = cleared by writing a 1 to this bit position. 2 last valid buffer completion interrupt (lvbci)? r/wc. 1 = last valid buffer has been processed. it remains active until cleared by software. this bit indicates the occurrence of the event signified by the last valid buffer being processed. thus, this is an event status bit that can be cleared by software once this event has been recognized. this event will cause an interrupt if the enable bit in the control register is set. the interrupt is cleared when the software clears this bit. in the case of transmits (pcm out, modem out) this bit is set, after the last valid buffer has been fetched (not after transmitting it). while in the case of receives , this bit is set after the data for the last buffer has been written to memory. 0 = cleared by writing a 1 to this bit position. 1 current equals last valid (celv)? ro. 1 = current index is equal to the value in the last valid index register, and the buffer pointed to by the civ has been processed (i.e., after the last valid buffer has been processed). this bit is very similar to bit 2, except this bit reflects the state rather than the event. this bit reflects the state of the controller, and remains set until the controller exits this state. 0 = cleared by hardware when controller exists state (i.e., until a new value is written to the lvi register.) 0 dma controller halted (dch) ?ro. 1 = halted. this could happen because of the start/stop bit being cleared, or it could happen once the controller has processed the last valid buffer (in which case it will set bit 1 and halt). ac?97 audio controller registers (d31:f5) 13-12 82801BA ich2 and 82801BAm ich2-m datasheet 13.2.5 x _picb?position in current buffer register i/o address: nabmbar + 08h (pipicb), attribute: ro (word access only) nabmbar + 18h (popicb), nabmbar + 28h (mcpicb) default value: 0000h size: 16 bits lockable: no power well: core this register can be accessed only as a word (16 bits). 13.2.6 x _piv?prefetched index value register i/o address: nabmbar + 0ah (pipiv), attribute: ro nabmbar + 1ah (popiv), nabmbar + 2ah (mcpiv) default value: 00h size: 8 bits lockable: no power well: core bit description 15:0 position in current buffer[15:0] ?ro. these bits represent the number of dwords remaining to be processed in the current buffer; the number of samples not yet read from memory (in the case of reads from memory) or not yet written to memory (in the case of writes to memory), irrespective of the number of samples that have been transmitted/received across ac-link. bit description 7:5 hardwired to 0. 4:0 prefetched index value[4:0] ?ro. these bits represent which buffer descriptor in the list has been prefetched. the bits in this register are also modulo 32 and roll over after they reach 31. 82801BA ich2 and 82801BAm ich2-m datasheet 13-13 ac?97 audio controller registers (d31:f5) 13.2.7 x _cr?control register i/o address: nabmbar + 0bh (picr), attribute: r/w nabmbar + 1bh (pocr), nabmbar + 2bh (mccr) default value: 00h size: 8 bits lockable: no power well: core bit description 7:5 reserved. 4 interrupt on completion enable (ioce) ?r/w. this bit controls whether or not an interrupt occurs when a buffer completes with the ioc bit set in its descriptor. 0 = disable. interrupt will not occur. 1 = enable. 3 fifo error interrupt enable (feie) ?r/w. this bit controls whether the occurrence of a fifo error will cause an interrupt or not. 0 = disable. bit 4 in the status register will be set; however, the interrupt will not occur. 1 = enable. interrupt will occur. 2 last valid buffer interrupt enable (lvbie) ?r/w. this bit controls whether the completion of the last valid buffer will cause an interrupt or not. 0 = disable. bit 2 in the status register will still be set; however, the interrupt will not occur. 1 = enable. 1 reset registers (rr) ?r/w (special). 1 = contents of all bus master related registers to be reset, except the interrupt enable bits (bit 4,3,2 of this register). software needs to set this bit but need not clear it since the bit is self clearing. this bit must be set only when the run/pause bit is cleared. setting it when the run bit is set will cause undefined consequences. 0 = removes reset condition. 0 run/pause bus master (rpbm) ?r/w. 0 = pause bus master operation. this results in all state information being retained (i.e., master mode operation can be stopped and then resumed). 1 = run. bus master operation starts. ac?97 audio controller registers (d31:f5) 13-14 82801BA ich2 and 82801BAm ich2-m datasheet 13.2.8 glob_cnt?global control register i/o address: nabmbar + 2ch attribute: r/w (dword access only) default value: 00000000h size: 32 bits lockable: no power well: core this register can be accessed only as a dword (32 bits). bit description 31:22 reserved. 21:20 pcm 4/6 enable ?r/w. configures pcm output for 2, 4 or 6 channel mode. 00 = 2-channel mode (default) 01 = 4-channel mode 10 = 6-channel mode 11 = reserved 19:6 reserved. 5 secondary resume interrupt enable? r/w. 0 = disable. 1 = enable an interrupt to occur when the secondary codec causes a resume event on the ac-link. 4 primary resume interrupt enable? r/w. 0 = disable. 1 = enable an interrupt to occur when the primary codec causes a resume event on the ac-link. 3 aclink shut off? r/w. 0 = normal operation. 1 = drive all ac?97 outputs low and turn off all ac?97 input buffer enables 2 ac?97 warm reset? r/w (special). 0 = normal operation. 1 = writing a 1 to this bit causes a warm reset to occur on the ac-link. the warm reset will awaken a suspended codec without clearing its internal registers. if software attempts to perform a warm reset while bit_clk is running, the write will be ignored and the bit will not change. this bit is self-clearing (it remains set until the reset completes and bit_clk is seen on the aclink, after which it clears itself). 1 ac ?97 cold reset#? r/w. 0 = writing a 0 to this bit causes a cold reset to occur throughout the ac ?97 circuitry. all data in the controller and the codec will be lost. software needs to clear this bit no sooner than the minimum number of ms have elapsed. 1 = this bit defaults to 0; thus, after reset, the driver needs to set this bit to a 1. the value of this bit is retained after suspends; thus, if this bit is set to a 1 prior to suspending, a cold reset is not generated automatically upon resuming. note: this bit is in the resume well, not in the core well. 0 gpi interrupt enable (gie)? r/w. this bit controls whether the change in status of any gpi causes an interrupt. 0 = bit 0 of the global status register is set, but no interrupt is generated. 1 = the change on value of a gpi causes an interrupt and sets bit 0 of the global status register. 82801BA ich2 and 82801BAm ich2-m datasheet 13-15 ac?97 audio controller registers (d31:f5) 13.2.9 glob_sta?global status register i/o address: nabmbar + 30h attribute: ro, r/w, r/wc (dword access only) default value: 00300000h size: 32 bits lockable: no power well: core this register can be accessed only as a dword (32 bits). bit description 31:22 reserved. 21 6 channel capability (6ch_cap)? ro. hardwired to 1. 0 = the ac ?97 controller does not support 6-channel pcm audio output. 1 = the ac ?97 controller supports 6-channel pcm audio output. 20 4 channel capability (4ch_cap)? ro. hardwired to 1. 0 = the ac ?97 controller does not support 4-channel pcm audio output. 1 = the ac ?97 controller supports 4-channel pcm audio output. 19:18 reserved. 17 md3? r/w. power down semaphore for modem. this bit exists in the suspend well and maintains context across power states (except g3). the bit has no hardware function. it is used by software in conjunction with the ad3 bit to coordinate the entry of the two codecs into d3 state. 16 ad3? r/w. power down semaphore for audio. this bit exists in the suspend well and maintains context across power states (except g3). the bit has no hardware function. it is used by software in conjunction with the md3 bit to coordinate the entry of the two codecs into d3 state. 15 read completion status (rcs)? r/wc. this bit indicates the status of codec read completions. 0 = a codec read completes normally. 1 = a codec read results in a time-out. the bit remains set until being cleared by software writing a 1 to the bit location. 14 bit 3 of slot 12? ro. display bit 3 of the most recent slot 12. 13 bit 2 of slot 12? ro. display bit 2 of the most recent slot 12. 12 bit 1 of slot 12? ro. display bit 1 of the most recent slot 12. 11 secondary resume interrupt (sri)? r/wc. this bit indicates that a resume event occurred on ac_sdin[1]. 1 = resume event occurred 0 = cleared by writing a 1 to this bit position. 10 primary resume interrupt (pri)? r/wc. this bit indicates that a resume event occurred on ac_sdin[0]. 1 = resume event occurred 0 = cleared by writing a 1 to this bit position. 9 secondary codec ready (scr)? ro. reflects the state of the codec ready bit in ac_sdin[1]. bus masters ignore the condition of the codec ready bits, so software must check this bit before starting the bus masters. once the codec is ?ready?, it must never go ?not ready? spontaneously. 0 = not ready. 1 = ready. 8 primary codec ready (pcr)? ro. reflects the state of the codec ready bit in ac_sdin [0]. bus masters ignore the condition of the codec ready bits, so software must check this bit before starting the bus masters. once the codec is ?ready?, it must never go ?not ready? spontaneously. 0 = not ready. 1 = ready. 7 mic in interrupt (mint)? ro. this bit indicates that one of the mic in channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. ac?97 audio controller registers (d31:f5) 13-16 82801BA ich2 and 82801BAm ich2-m datasheet 13.2.10 cas?codec access semaphore register i/o address: nabmbar + 34h attribute: r/w default value: 00h size: 8 bits lockable: no power well: core 6 pcm out interrupt (point)? ro. this bit indicates that one of the pcm out channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 5 pcm in interrupt (piint)? ro. this bit indicates that one of the pcm in channel interrupts occurred. 1 = interrupt occurred. 0 = 0 = when the specific interrupt is cleared, this bit will be cleared. 4:3 reserved 2 modem out interrupt (moint)? ro. this bit indicates that one of the modem out channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 1 modem in interrupt (miint)? ro. this bit indicates that one of the modem in channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 0 gpi status change interrupt (gsci)? rwc. this bit reflects the state of bit 0 in slot 12, and is set whenever bit 0 of slot 12 is set. this happens when the value of any of the gpios currently defined as inputs changes. 1 = input changed. 0 = cleared by writing a 1 to this bit position. bit description bit description 7:1 reserved. 0 codec access semaphore (cas)? r/w (special). this bit is read by software to check whether a codec access is currently in progress. 0 = no access in progress. 1 = the act of reading this register sets this bit to 1. the driver that read this bit can then perform an i/o access. once the access is completed, hardware automatically clears this bit. 82801BA ich2 and 82801BAm ich2-m datasheet 14-1 ac?97 modem controller registers (d31:f6) ac?97 modem controller registers (d31:f6) 14 14.1 ac?97 modem pci configuration space (d31:f6) note: registers that are not shown should be treated as reserved (see section 6.2 for details). note: refer to the specification update for the value of the revision id register 14.1.1 vid?vendor identification register (modem?d31:f6) address offset: 01h?00h attribute: ro default value: 8086 size: 16 bits lockable: no power well: core table 14-1. pci configuration map (modem?d31:f6) offset mnemonic register default access 00h?01h vid vendor identification 8086 ro 02h?03h did device identification 2446h ro 04h?05h pcicmd pci command 0000 r/w 06h?07h pcista pci device status 0280h r/wc 08h rid revision identification see note ro 09h pi programming interface 00 ro 0ah scc sub class code 03h ro 0bh bcc base class code 07h ro 0eh hedt header type 00 ro 0fh ? reserved ? ? 10h?13h mmbar modem mixer base address 00000001h r/w 14h?17h mbar modem base address 00000001h r/w 18h?1bh ? reserved 00000001h ? 1ch?2bh ? reserved ? ? 2ch?2dh svid subsystem vendor id 0000h write-once 2eh?2fh sid subsystem id 0000h write-once 30h?3bh ? reserved ? ? 3ch intr_ln interrupt line 00h ro 3dh int_pn interrupt pin 02h ro 3eh?ffh ? reserved ? ? bit description 15:0 vendor id value. ac?97 modem controller registers (d31:f6) 14-2 82801BA ich2 and 82801BAm ich2-m datasheet 14.1.2 did?device identification register (modem?d31:f6) address offset: 03h?02h attribute: ro default value: 2446h size: 16 bits lockable: no power well: core 14.1.3 pcicmd?pci command register (modem?d31:f6) address offset: 05h?04h attribute: r/w default value: 0000h size: 16 bits lockable: no power well: core pcicmd is a 16-bit control register. refer to the pci 2.1 specification for complete details on each bit. bit description 15:0 device id value. bit description 15:10 reserved. read 0. 9 fast back to back enable (fbe). not implemented. hardwired to 0. 8 serr# enable (sen). not implemented. hardwired to 0. 7 wait cycle control (wcc). not implemented. hardwired to 0. 6 parity error response (per). not implemented. hardwired to 0. 5 vga palette snoop (vps). not implemented. hardwired to 0. 4 memory write and invalidate enable (mwi). not implemented. hardwired to 0. 3 special cycle enable (sce). not implemented. hardwired to 0. 2 bus master enable (bme) ?r/w. controls standard pci bus mastering capabilities. 0 = disable. 1 = enable 1 memory space (ms). hardwired to 0, ac ?97 does not respond to memory accesses. 0 i/o space (ios) ?r/w. this bit controls access to the i/o space registers. 0 = disable access. (default = 0). 1 = enable access to i/o space. the native pci mode base address register should be programmed prior to setting this bit. 82801BA ich2 and 82801BAm ich2-m datasheet 14-3 ac?97 modem controller registers (d31:f6) 14.1.4 pcista?device status register (modem?d31:f6) address offset: 07h?06h attribute: r/wc default value: 0280h size: 16 bits lockable: no power well: core pcista is a 16-bit status register. refer to the pci 2.1 specification for complete details on each bit. 14.1.5 rid?revision identification register (modem?d31:f6) address offset: 08h attribute: ro default value: see bit description size: 8 bits lockable: no power well: core 14.1.6 pi?programming interface register (modem?d31:f6) address offset: 09h attribute: ro default value: 00h size: 8 bits lockable: no power well: core bit description 15 detected parity error (dpe)?ro. not implemented. hardwired to 0. 14 serr# status (serrs)?ro. not implemented. hardwired to 0. 13 master-abort status (mas) ?r/wc. 1 = bus master ac ?97 interface function, as a master, generates a master abort. 0 = software clears this bit by writing a 1 to the bit position. 12 reserved. read as ?0?. 11 signaled target-abort status (sta)?ro. not implemented. hardwired to 0. 10:9 devsel# timing status (devt)?ro . this 2-bit field reflects the ich2's devsel# timing parameter. these read only bits indicate the ich2's devsel# timing when performing a positive decode. 8 data parity detected (dpd)?ro. not implemented. hardwired to 0. 7 fast back to back capable (fbc)?ro. hardwired to 1. this bit indicates that the ich2 as a target is capable of fast back-to-back transactions. 6 udf supported?ro. not implemented. hardwired to 0. 5 66 mhz capable?ro. hardwired to 0. 4:0 reserved. read as 0s. bit description 7:0 revision id value ?ro. refer to the specification update for the value of the revision id register bit description 7:0 programming interface value ?ro. ac?97 modem controller registers (d31:f6) 14-4 82801BA ich2 and 82801BAm ich2-m datasheet 14.1.7 scc?sub class code register (modem?d31:f6) address offset: 0ah attribute: ro default value: 03h size: 8 bits lockable: no power well: core 14.1.8 bcc?base class code register (modem?d31:f6) address offset: 0bh attribute: ro default value: 07h size: 8 bits lockable: no power well: core 14.1.9 hedt?header type register (modem?d31:f6) address offset: 0eh attribute: ro default value: 00h size: 8 bits lockable: no power well: core 14.1.10 mmbar?modem mixer base address register (modem?d31:f6) address offset: 10h?13h attribute: r/w default value: 00000001h size: 32 bits the native pci mode modem uses pci base address register #1 to request a contiguous block of i/o space that is to be used for the modem mixer software interface. the mixer requires 256 bytes of i/o space. all accesses to the mixer registers are forwarded over the ac-link to the codec where the registers reside. in the case of the split codec implementation accesses to the different codecs are differentiated by the controller by using address offsets 00h?7fh for the primary codec and address offsets 80h?feh for the secondary codec. bit description 7:0 sub class code value ?ro. 03h = generic modem. bit description 7:0 base class code value ?ro. 07h = simple communications controller. bit description 7:0 header value ?ro. 82801BA ich2 and 82801BAm ich2-m datasheet 14-5 ac?97 modem controller registers (d31:f6) 14.1.11 mbar?modem base address register (modem?d31:f6) address offset: 14h?17h attribute: r/w default value: 00000001h size: 32 bits the modem function uses pci base address register #1 to request a contiguous block of i/o space that is to be used for the modem software interface. the modem bus mastering register space requires 128 bytes of i/o space. all modem registers reside in the controller, therefore cycles are not forwarded over the ac-link to the codec. 14.1.12 svid?subsystem vendor id (modem?d31:f6) address offset: 2dh?2ch attribute: write-once default value: 0000h size: 16 bits lockable: no power well: core the svid register, in combination with the subsystem id register, enable the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to the register, the value can be read back. any subsequent writes will have no effect. bit description 31:16 hardwired to 0s 15:8 base address ?r/w. these bits are used in the i/o space decode of the modem interface registers. the number of upper bits that a device actually implements depends on how much of the address space the device will respond to. for the ac ?97 modem, the upper 16 bits are hardwired to 0, while bits 15:8 are programmable. this configuration yields a maximum i/o block size of 256 bytes for this base address. note: this address must align to a 256-byte boundary. 7:1 reserved. read as 0 0 resource type indicator (rte) ?ro. this bit is set to one, indicating a request for i/o space. bit description 31:16 hardwired to 0s 15:7 base address ?r/w. these bits are used in the i/o space decode of the modem interface registers. the number of upper bits that a device actually implements depends on how much of the address space the device will respond to. for the ac ?97 modem, the upper 16 bits are hardwired to 0, while bits 15:7 are programmable. this configuration yields a maximum i/o block size of 128 bytes for this base address. note: this address must align to a 128-byte boundary. 6:1 reserved. read as 0 0 resource type indicator (rte) ?ro. this bit is set to one, indicating a request for i/o space. bit description 15:0 subsystem vendor id value ?read/write-once. ac?97 modem controller registers (d31:f6) 14-6 82801BA ich2 and 82801BAm ich2-m datasheet 14.1.13 sid?subsystem id (modem?d31:f6) address offset: 2fh?2eh attribute: write-once default value: 0000h size: 16 bits lockable: no power well: core the sid register, in combination with the subsystem vendor id register, makes it possible for the operating environment to distinguish one audio subsystem from another. this register is implemented as a write-once register. once a value is written to the register, the value can be read back. any subsequent writes will have no effect. 14.1.14 intr_ln?interrupt line register (modem?d31:f6) address offset: 3ch attribute: r/w default value: 00h size: 8 bits lockable: no power well: core this register indicates which pci interrupt line is used for the ac?97 module interrupt. 14.1.15 int_pin?interrupt pin (modem?d31:f6) address offset: 3dh attribute: ro default value: 02h size: 8 bits lockable: no power well: core this register indicates which pci interrupt pin is used for the ac ?97 modem interrupt. the ac ?97 interrupt is internally ored to the interrupt controller with the pirqb# signal. bit description 15:0 subsystem id value ?read/write-once. bit description 7:0 interrupt line ?r/w. this data is not used by the ich2. it is used to communicate to software the interrupt line that the interrupt pin is connected to. bit description 7:3 reserved. 2:0 ac ?97 interrupt routing ?ro. hardwired to 010b to select pirqb#. 82801BA ich2 and 82801BAm ich2-m datasheet 14-7 ac?97 modem controller registers (d31:f6) 14.2 ac?97 modem i/o space (d31:f6) in the case of the split codec implementation accesses to the modem mixer registers in different codecs are differentiated by the controller by using address offsets 00h?7fh for the primary codec and address offsets 80h?feh for the secondary codec. table 14-2 shows the register addresses for the modem mixer registers. note: 1. registers in bold are multiplexed between audio and modem functions 2. registers in italics are for functions not supported by the ich2 3. software should not try to access reserved registers 4. the ich2 supports a modem codec as either primary or secondary, but does not support two modem codecs. the global control (glob_cnt) and global status (glob_sta) registers are aliased to the same global registers in the audio and modem i/o space. therefore a read/write to these registers in either audio or modem i/o space affects the same physical register. these registers exist in i/o space and reside in the ac ?97 controller. the two channels, modem in and modem out, each have their own set of bus mastering registers. the following register descriptions apply to both channels. the naming prefix convention used is as follows: ? mi = modem in channel ? mo = modem out channel table 14-2. ich2 modem mixer register configuration register mmbar exposed registers (d31:f6) primary secondary name 00h:38h 80h:b8h intel reserved 3ch bch extended modem id 3eh beh extended modem status/control 40h c0h line 1 dac/adc rate 42h c2h line 2 dac/adc rate 2 44h c4h handset dac/adc rate 2 46h c6h line 1 dac/adc level mute 48h c8h line 2 dac/adc level mute 2 4ah cah handset dac/adc level mute 2 4ch cch gpio pin configuration 4eh ceh gpio polarity/type 50h d0h gpio pin sticky 52h d2h gpio pin wake up 54h d4h gpio pin status 56h d6h misc. modem afe stat/ctrl 58h 1 d8h vendor reserved 7ah 1 fah vendor reserved 7ch 1 fch vendor id1 7eh 1 feh vendor id2 ac?97 modem controller registers (d31:f6) 14-8 82801BA ich2 and 82801BAm ich2-m datasheet note: 1. mi = modem in channel; mo = modem out channel 14.2.1 x _bdbar?buffer descriptor list base address register i/o address: mbar + 00h (mibdbar), attribute: r/w (dword access only) mbar + 10h (mobdbar) default value: 00000000h size: 32bits lockable: no power well: core this register can be accessed only as a dword (32 bits). table 14-3. modem registers offset mnemonic name default access 00h mi_bdbar modem in buffer descriptor list base address register 00000000h r/w 04h mi_civ modem in current index value register 00h r 05h mi_lvi modem in last valid index register 00h r/w 06h mi_sr modem in status register 0001h r/w 08h mi_picb modem in position in current buffer register 00h r 0ah mi_piv modem in prefetch index value register 00h ro 0bh mi_cr modem in control register 00h r/w 10h mo_bdbar modem out buffer descriptor list base address register 00000000h r/w 14h mo_civ modem out current index value register 00h ro 15h mo_lvi modem out last valid register 00h r/w 16h mo_sr modem out status register 0001h r/w 18h mi_picb modem in position in current buffer register 00h ro 1ah mo_piv modem out prefetched index register 00h ro 1bh mo_cr modem out control register 00h r/w 3ch glob_cnt global control 00000000h r/w 40h glob_sta global status 00000000h ro 44h acc_sema codec write semaphore register 00h r/w bit description 31:3 buffer descriptor list base address[31:3]? r/w. these bits represent address bits 31:3. the entries should be aligned on 8 byte boundaries. 2:0 hardwired to 0. 82801BA ich2 and 82801BAm ich2-m datasheet 14-9 ac?97 modem controller registers (d31:f6) 14.2.2 x _civ?current index value register i/o address: mbar + 04h (miciv), attribute: ro mbar + 14h (mociv), default value: 00h size: 8bits lockable: no power well: core 14.2.3 x _lvi?last valid index register i/o address: mbar + 05h (milvi), attribute: r/w mbar + 15h (molvi) default value: 00h power well: core bit description 7:5 hardwired to 0. 4:0 current index value [4:0]? ro. these bits represent which buffer descriptor within the list of 16 descriptors is being processed currently. as each descriptor is processed, this value is incremented. bit description 7:5 hardwired to 0 4:0 last valid index [4:0]? r/w. these bits indicate the last valid descriptor in the list. this value is updated by software as it prepares new buffers and adds to the list. ac?97 modem controller registers (d31:f6) 14-10 82801BA ich2 and 82801BAm ich2-m datasheet 14.2.4 x _sr?status register i/o address: mbar + 06h (misr), attribute: r/wc (word access only) mbar + 16h (mosr) default value: 0001h size: 16 bits lockable: no power well: core this register can be accessed only as a word (16 bits). bit description 15:5 reserved. 4 fifo error (fifoe)? r/wc. 1 = fifo error occurs. 0 = cleared by writing a 1 to this bit position. modem in: fifo error indicates a fifo overrun. the fifo pointers do not increment, the incoming data is not written into the fifo, thereby being lost. modem out: fifo error indicates a fifo underrun. the sample transmitted in this case should be the last valid sample. the ich2 sets the fifoe bit if the under-run or overrun occurs when there are more valid buffers to process. 3 buffer completion interrupt status (bcis)? r/wc. 1 = set by the hardware after the last sample of a buffer has been processed, and if the interrupt on completion (ioc) bit is set in the command byte of the buffer descriptor. remains active until software clears bit. 0 = cleared by writing a 1 to this bit position. 2 last valid buffer completion interrupt (lvbci)? r/wc. 1 = set by hardware when last valid buffer has been processed. it remains active until cleared by software. this bit indicates the occurrence of the event signified by the last valid buffer being processed. thus, this is an event status bit that can be cleared by software once this event has been recognized. this event will cause an interrupt if the enable bit in the control register is set. the interrupt is cleared when the software clears this bit. in the case of transmits (pcm out, modem out) this bit is set, after the last valid buffer has been fetched (not after transmitting it) while in the case of receives, this bit is set after the data for the last buffer has been written to memory. 0 = cleared by writing a 1 to this bit position 1 current equals last valid (celv)? ro. 1 = current index is equal to the value in the last valid index register, and the buffer pointed to by the civ has been processed (i.e., after the last valid buffer has been processed). this bit is very similar to bit 2, except, this bit reflects the state rather than the event. this bit reflects the state of the controller, and remains set until the controller exits this state. 0 = hardware clears when controller exists state (i.e., until a new value is written to the lvi register). 0 dma controller halted (dch)? ro. 1 = dma controller is halted. this could happen because of the start/stop bit being cleared, or it could happen once the controller has processed the last valid buffer (in which case it will set bit 1 and halt). 82801BA ich2 and 82801BAm ich2-m datasheet 14-11 ac?97 modem controller registers (d31:f6) 14.2.5 x _picb?position in current buffer register i/o address: mbar + 08h (mipicb), attribute: ro (word access only) mbar + 18h (mopicb), default value: 0000h size: 16 bits lockable: no power well: core this register can be accessed only as a word (16 bits). 14.2.6 x _piv?prefetch index value register i/o address: mbar + 0ah (mipiv), attribute: ro mbar + 1ah (mopiv) default value: 00h size: 8 bits lockable: no power well: core 14.2.7 x _cr?control register i/o address: mbar + 0bh (micr), attribute: r/w mbar + 1bh (mocr) default value: 00h size: 8 bits lockable: no power well: core bit description 15:0 position in current buffer[15:0]? ro. these bits represent the number of dwords left to be processed in the current buffer. bit description 7:5 hardwired to 0 4:0 prefetched index value [4:0]? ro. these bits represent which buffer descriptor in the list has been prefetched. bit description 7:5 reserved. 4 interrupt on completion enable (ioce)? r/w. this bit controls whether or not an interrupt occurs when a buffer completes with the ioc bit set in its descriptor. 0 = disable. 1 = enable. 3 fifo error interrupt enable (feie)? r/w. this bit controls whether the occurrence of a fifo error will cause an interrupt or not. 0 = disable. bit 4 in the status register will be set, but the interrupt will not occur. 1 = enable. interrupt will occur 2 last valid buffer interrupt enable (lvbie)? r/w. this bit controls whether the completion of the last valid buffer will cause an interrupt or not. 0 = disable. bit 2 in the status register will still be set, but the interrupt will not occur. 1 = enable. 1 reset registers (rr)? r/w (special). 1 = contents of all registers to be reset, except the interrupt enable bits (bit 4,3,2 of this register). software needs to set this bit. it must be set only when the run/pause bit is cleared. setting it when the run bit is set will cause undefined consequences. this bit is self-clearing (software does not need to clear it). 0 = removes reset condition. ac?97 modem controller registers (d31:f6) 14-12 82801BA ich2 and 82801BAm ich2-m datasheet 14.2.8 glob_cnt?global control register i/o address: mbar + 3ch attribute: r/w (dword access only) default value: 00000000h size: 32 bits lockable: no power well: core this register can be accessed only as a dword (32 bits). 0 run/pause bus master (rpbm)? r/w. 0 = pause bus master operation. this results in all state information being retained (i.e., master mode operation can be stopped and then resumed). 1 = run. bus master operation starts. bit description bit description 31:6 reserved. 5 secondary resume interrupt enable? r/w. 0 = disable. 1 = enable an interrupt to occur when the secondary codec causes a resume event on the ac-link. 4 primary resume interrupt enable? r/w. 0 = disable. 1 = enable an interrupt to occur when the primary codec causes a resume event on the ac-link. 3 aclink shut off? r/w. 0 = normal operation. 1 = disable the ac-link signals (drive all ac?97 outputs low and turn off all ac?97 input buffer enables) 2 ac?97 warm reset? r/w (special). 1 = writing a 1 to this bit causes a warm reset to occur on the ac-link. the warm reset will awaken a suspended codec without clearing its internal registers. if software attempts to perform a warm reset while bit_clk is running, the write will be ignored and the bit will not be changed. a warm reset can only occur in the absence of bit_clk. 0 = this bit is self-clearing (it clears itself after the reset has occurred and bit_clk has started). 1 ac?97 cold reset#? r/w (special). 0 = writing a 0 to this bit causes a cold reset to occur throughout the ac?97 circuitry. all data in the codec will be lost. software needs to clear this bit no sooner than after 1usec has elapsed. this bit reflects the state of the ac_rst# pin. the ich2 clears this bit to ?0? upon entering s3/s4/s5 sleep states and pcirst#. 0 gpi interrupt enable (gie)? r/w. this bit controls whether the change in status of any gpi causes an interrupt. 0 = bit 0 of the global status register is set, but an interrupt is not generated. 1 = the change on value of a gpi causes an interrupt and sets bit 0 of the global status register. 82801BA ich2 and 82801BAm ich2-m datasheet 14-13 ac?97 modem controller registers (d31:f6) 14.2.9 glob_sta?global status register i/o address: mbar + 40h attribute: ro, r/w, r/wc (dword access only) default value: 00300000h size: 32 bits lockable: no power well: core this register can be accessed only as a dword (32 bits). bit description 31:22 reserved. 21 6 channel capability (6ch_cap)? ro. hardwired to 1. 0 = the ac ?97 controller does not support 6-channel pcm audio output. 1 = the ac ?97 controller supports 6-channel pcm audio output. 20 4 channel capability (4ch_cap)? ro. hardwired to 1. 0 = the ac ?97 controller does not support 4-channel pcm audio output. 1 = the ac ?97 controller supports 4-channel pcm audio output. 19:18 reserved. 17 md3? r/w. power down semaphore for modem. this bit exists in the suspend well and maintains context across power states (except g3). the bit has no hardware function. it is used by software in conjunction with the ad3 bit to coordinate the entry of the two codecs into d3 state. 16 ad3? r/w. power down semaphore for audio. this bit exists in the suspend well and maintains context across power states (except g3). the bit has no hardware function. it is used by software in conjunction with the md3 bit to coordinate the entry of the two codecs into d3 state. 15 read completion status (rcs)? r/w. this bit indicates the status of codec read completions. 0 = a codec read completes normally. 1 = a codec read results in a time-out. the bit remains set until being cleared by software. 14 bit 3 of slot 12? ro. display bit 3 of the most recent slot 12 13 bit 2 of slot 12? ro. display bit 2 of the most recent slot 12 12 bit 1 of slot 12? ro. display bit 1 of the most recent slot 12 11 secondary resume interrupt (sri)? r/wc. this bit indicates that a resume event occurred on ac_sdin[1]. 1 = resume event occurred 0 = cleared by writing a 1 to this bit position. 10 primary resume interrupt (pri)? r/wc. this bit indicates that a resume event occurred on ac_sdin[0]. 1 = resume event occurred 0 = cleared by writing a 1 to this bit position. 9 secondary codec ready (scr)? ro. reflects the state of the codec ready bit in ac_sdin[1]. bus masters ignore the condition of the codec ready bits, so software must check this bit before starting the bus masters. once the codec is ?ready?, it must never go ?not ready? spontaneously. 0 = not ready. 1 = ready. 8 primary codec ready (pcr)? ro. reflects the state of the codec ready bit in ac_sdin [0]. bus masters ignore the condition of the codec ready bits, so software must check this bit before starting the bus masters. once the codec is ?ready?, it must never go ?not ready? spontaneously. 0 = not ready. 1 = ready. 7 mic in interrupt (mint)? ro. this bit indicates that one of the mic in channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. ac?97 modem controller registers (d31:f6) 14-14 82801BA ich2 and 82801BAm ich2-m datasheet note: on reads from a codec, the controller will give the codec a maximum of 4 frames to respond, after which if no response is received, it will return a dummy read completion to the processor (with all phs on the data) and also set the read completion status bit in the global status register. 14.2.10 cas?codec access semaphore register i/o address: nabmbar + 44h attribute: r/w default value: 00h size: 8 bits lockable: no power well: core 6 pcm out interrupt (point)? ro. this bit indicates that one of the pcm out channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 5 pcm in interrupt (piint)? ro. this bit indicates that one of the pcm in channel interrupts occurred. 1 = interrupt occurred. 0 = 0 = when the specific interrupt is cleared, this bit will be cleared. 4:3 reserved 2 modem out interrupt (moint)? ro. this bit indicates that one of the modem out channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 1 modem in interrupt (miint)? ro. this bit indicates that one of the modem in channel interrupts occurred. 1 = interrupt occurred. 0 = when the specific interrupt is cleared, this bit will be cleared. 0 gpi status change interrupt (gsci) ?rwc. this bit reflects the state of bit 0 in slot 12, and is set when bit 0 of slot 12 is set. this happens when the value of any of the gpios currently defined as inputs changes. 1 = input changed. 0 = cleared by writing a 1 to this bit position. bit description bit description 7:1 reserved. 0 codec access semaphore (cas)? r/w (special). this bit is read by software to check whether a codec access is currently in progress. 0 = no access in progress. 1 = the act of reading this register sets this bit to 1. the driver that read this bit can then perform an i/o access. once the access is completed, hardware automatically clears this bit. 82801BA ich2 and 82801BAm ich2-m datasheet 15-1 pinout and package information pinout and package information 15 15.1 pinout this section contains the ich2 82801BA and ich2-m 82801BAm ballout information. figure 15-1 and figure 15-2 provide a graphical illustration of how the ballout maps to the 360 ebga package for both the ich2 82801BA and 82801BAm ich2-m. table 15-1 provides the ballout for the ich2 82801BA, listed alphabetically by signal name. table 15-2 provides the ballout for the ich2-m 82801BAm, listed alphabetically by signal name. pinout and package information 15-2 82801BA ich2 and 82801BAm ich2-m datasheet figure 15-1. ich2 82801BA and ich2-m 82801BAm ballout (top view ? left side) 1 2 34567891011 a vss vss hlcomp hl0 hl2 hl_stb hl_stb# hl5 hl7 vss ignne# b vss vss vss hubref hl1 hl3 hl4 hl6 vss vss nmi c #n/a vss vss vss hl11 hl9 hl10 hl8 vss stpclk# intr d #n/a vcc1_8 vss clk66 vss vss vss vss vss vcc1_8 a20m# e #n/a #n/a #n/a #n/a vcc1_8 vss vss vss vss f lan_txd2 lan_txd1 lan_txd0 #n/a vccsus3_3 (ich2) vcclan3_3 (ich2-m) g lan_rxd1 lan_rxd0 lan_clk #n/a vccsus3_3 (ich2) vcclan3_3 (ich2-m) h lan_rxd2 lan_rstsync #n/a #n/a vccsus1_8 (ich2) vcclan1_8 (ich2-m) j #n/a #n/a ee_shclk ee_dout vccsus1_8 (ich2) vcclan1_8 (ich2-m) vss vss vss k vss v5ref1 ee_din ee_cs vss vss vss l gpio21 (ich2) c3_stat# / gpio21 (ich2-m) gnta# /gpio16 reqb# / req5# / gpio1 gntb# / gnt5# / gpio17 vss vss vss m gnt1# gnt0# reqa# / gpio0 pirqh# vss vss vss n pirqg# / gpio4 pirqf#/ gpio3 pirqe# pirqd# vss vss vss p pirqa# pirqb# pirqc# req4# vcc1_8 vss vss vss r gnt4# req0# req1# gnt2# vcc3_3 t req2# gnt3# ad30 ad28 vcc3_3 u ad26 ad24 ad22 ad20 vcc3_3 v ad18 ad16 frame# trdy# vcc3_3 vcc3_3 vcc3_3 vcc3_3 vcc1_8 w stop# par ad11 ad4 ad3 ad10 serr# irdy# ad21 ad27 pciclk y ad15 ad13 ad9 ad2 ad5 ad12 perr# c/be2# ad23 ad29 gpio6 (ich2) agpbusy# (ich2-m) aa vss vss c/be0# ad0 ad7 ad14 plock# ad17 c/be3# ad31 gpio7 ab vss vss ad6 ad1 ad8 c/be1# devsel# ad19 ad25 req3# lframe# / fwh4 1 2 34567891011 82801BA ich2 and 82801BAm ich2-m datasheet 15-3 pinout and package information figure 15-2. ich2 82801BA and ich2-m 82801BAm ballout (top view ? right side) 12 13 14 15 16 17 18 19 20 21 22 cpuslp# cpupwrgd gpio23 (ich2) gmuxsel# (ich2-m) gpio18 (ich2) stp_pci# (ich2-m) sda0 siordy sdd15 sdd13 sdd3 vss vss a smi# rcin# gpio22 (ich2) cpuperf# (ich2-m) vrmpwrgd (ich2) vgate / vrmpwrgd (ich2-m) sda2 sddack# sddreq sdd1 sdd11 vss vss b init# a20gate gpio20 (ich2) stp_cpu# (ich2-m) sdcs1# irq15 sdiow# sdd14 sdd12 sdd4 sdd5 sdd9 c v_cpu_io v_cpu_io gpio19 (ich2) slp_s1# (ich2-m) sdcs3# sda1 sdior# sdd0 sdd2 sdd10 sdd8 sdd6 d vcc3_3 vcc3_3 vcc3_3 vcc3_3 vcc3_3 pdcs3# sdd7 pdcs1# pda2 e vcc3_3 pda1 pda0 irq14 pddack# f vcc3_3 pdior# piordy pdiow# pddreq g vcc3_3 pdd0 pdd15 pdd14 pdd1 h vss vss vss vcc3_3 pdd2 pdd13 pdd12 pdd3 j vss vss vss vcc1_8 pdd11 pdd4 pdd10 k vss vss vss vcc1_8 pdd5 pdd9 pdd8 l vss vss vss clk14 v5ref2 pdd6 pdd7 m vss vss vss apicd1 apicclk serirq spkr n vss vss vss vcc3_3 ac_sync clk48 ac_sdout apicd0 p vcc3_3 ac_bitclk pwrok rsmrst# ferr# r vccsus3_3 intruder# rtcrst# vbias rtcx2 t vccsus3_3 smlink0 tp0(ich2) batlow# (ich2-m) vccrtc rtcx1 u vccsus1_8 vccsus1_8 vccsus1_8 vccsus3_3 vccsus3_3 v5ref_sus smlink1 gpio24 (ich2) clkrun# (ich2-m) ac_rst# v lad1 / fwh1 ldrq1# gpio12 gpio25 slp_s3# usbp0p usbp2p oc0# oc3# pwrbtn# ac_sdin1 w lad0 / fwh0 ldrq0# gpio8 pme# rsm_pwrok (ich2) lan_pwrok# (ich2-m) susstat# usbp0n usbp2n oc1# oc2# ac_sdin0 y fs0 thrm# gpio28 pcirst# smbdata ri# susclk usbp1n usbp3n vss vss aa lad3 / fwh3 lad2 / fwh2 gpio27 gpio13 smbclk smbalert# / gpio11 slp_s5# usbp1p usbp3p vss vss ab 12 13 14 15 16 17 18 19 20 21 22 pinout and package information 15-4 82801BA ich2 and 82801BAm ich2-m datasheet table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number sdd03 a20 a20gate c13 a20m# d11 ac_bitclk r19 ac_rst# v22 ac_sdin0 y22 ac_sdin1 w22 ac_sdout p21 ac_sync p19 ad0 aa4 ad1 ab4 ad2 y4 ad3 w5 ad4 w4 ad5 y5 ad6 ab3 ad7 aa5 ad8 ab5 ad9 y3 ad10 w6 ad11 w3 ad12 y6 ad13 y2 ad14 aa6 ad15 y1 ad16 v2 ad17 aa8 ad18 v1 ad19 ab8 ad20 u4 ad21 w9 ad22 u3 ad23 y9 ad24 u2 ad25 ab9 ad26 u1 ad27 w10 ad28 t4 ad29 y10 ad30 t3 ad31 aa10 apicclk n20 apicd0 p22 apicd1 n19 c/be0# aa3 c/be1# ab6 c/be2# y8 c/be3# aa9 clk14 m19 clk48 p20 clk66 d4 cpupwrgd a13 cpuslp# a12 devsel# ab7 ee_cs k4 ee_din k3 ee_dout j4 ee_shclk j3 ferr# r22 frame# v3 fs0 aa12 gnt0# m2 gnt1# m1 gnt2# r4 gnt3# t2 gnt4# r1 gnta# / gpio16 l2 gntb# / gnt5# / gpio17 l4 gpio6 y11 gpio7 aa11 gpio8 y14 gpio12 w14 gpio13 ab15 gpio18 a15 gpio19 d14 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number pinout and package information 82801BA ich2 and 82801BAm ich2-m datasheet 15-5 gpio20 c14 gpio21 l1 gpio22 b14 gpio23 a14 gpio24 v21 gpio25 w15 gpio27 ab14 gpio28 aa14 hl_stb a6 hl_stb# a7 hl0 a4 hl1 b5 hl2 a5 hl3 b6 hl4 b7 hl5 a8 hl6 b8 hl7 a9 hl8 c8 hl9 c6 hl10 c7 hl11 c5 hlcomp a3 hubref b4 ignne# a11 init# c12 intr c11 intruder# t19 irdy# w8 irq14 f21 irq15 c16 lad0 / fwh0 y12 lad1 / fwh1 w12 lad2 / fwh2 ab13 lad3 / fwh3 ab12 lan_clk g3 lan_rstsync h2 lan_rxd0 g2 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number lan_rxd1 g1 lan_rxd2 h1 lan_txd0 f3 lan_txd1 f2 lan_txd2 f1 ldrq0# y13 ldrq1# w13 lframe# / fwh4 ab11 nmi b11 oc0# w19 oc1# y20 oc2# y21 oc3# w20 par w2 pciclk w11 pcirst# aa15 pda0 f20 pda1 f19 pda2 e22 pdcs1# e21 pdcs3# e19 pdd0 h19 pdd1 h22 pdd2 j19 pdd3 j22 pdd4 k21 pdd5 l20 pdd6 m21 pdd7 m22 pdd8 l22 pdd9 l21 pdd10 k22 pdd11 k20 pdd12 j21 pdd13 j20 pdd14 h21 pdd15 h20 pddack# f22 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number pinout and package information 15-6 82801BA ich2 and 82801BAm ich2-m datasheet pddreq g22 pdior# g19 pdiow# g21 perr# y7 piordy g20 pirqa# p1 pirqb# p2 pirqc# p3 pirqd# n4 pirqe# n3 pirqf# / gpio3 n2 pirqg# / gpio4 n1 pirqh# m4 plock# aa7 pme# y15 pwrbtn# w21 pwrok r20 rcin# b13 req0# r2 req1# r3 req2# t1 req3# ab10 req4# p4 reqa# / gpio0 m3 reqb# / req5#/ gpio1 l3 ri# aa17 rsm_pwrok y16 rsmrst# r21 rtcrst# t20 rtcx1 u22 rtcx2 t22 sda0 a16 sda1 d16 sda2 b16 sdcs1# c15 sdcs3# d15 sdd0 d18 sdd1 b19 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number sdd2 d19 sdd4 c20 sdd5 c21 sdd6 d22 sdd7 e20 sdd8 d21 sdd9 c22 sdd10 d20 sdd11 b20 sdd12 c19 sdd13 a19 sdd14 c18 sdd15 a18 sddack# b17 sddreq b18 sdior# d17 sdiow# c17 serirq n21 serr# w7 siordy a17 slp_s3# w16 slp_s5# ab18 smbalert# / gpio11 ab17 smbclk ab16 smbdata aa16 smi# b12 smlink0 u19 smlink1 v20 spkr n22 stop# w1 stpclk# c10 susclk aa18 susstat# y17 thrm# aa13 tp0 u20 trdy# v4 usbp0n y18 usbp0p w17 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number pinout and package information 82801BA ich2 and 82801BAm ich2-m datasheet 15-7 usbp1n aa19 usbp1p ab19 usbp2n y19 usbp2p w18 usbp3n aa20 usbp3p ab20 v_cpu_io d12 v_cpu_io d13 v5ref_sus v19 v5ref1 k2 v5ref2 m20 vbias t21 vcc1_8 d10 vcc1_8 d2 vcc1_8 k19 vcc1_8 l19 vcc1_8 p5 vcc1_8 v9 vcc1_8 e5 vcc3_3 e14 vcc3_3 e15 vcc3_3 e16 vcc3_3 e17 vcc3_3 e18 vcc3_3 f18 vcc3_3 g18 vcc3_3 h18 vcc3_3 j18 vcc3_3 p18 vcc3_3 r18 vcc3_3 r5 vcc3_3 t5 vcc3_3 u5 vcc3_3 v5 vcc3_3 v6 vcc3_3 v7 vcc3_3 v8 vccrtc u21 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number vccsus1_8 h5 vccsus1_8 j5 vccsus1_8 v14 vccsus1_8 v15 vccsus1_8 v16 vccsus3_3 f5 vccsus3_3 g5 vccsus3_3 t18 vccsus3_3 u18 vccsus3_3 v17 vccsus3_3 v18 vrmpwrgd b15 vss d7 vss d8 vss d9 vss e6 vss e7 vss e8 vss e9 vss j10 vss j11 vss j12 vss j13 vss j14 vss j9 vss k1 vss k10 vss k11 vss k12 vss k13 vss k14 vss k9 vss l10 vss l11 vss a1 vss a10 vss a2 vss a21 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number pinout and package information 15-8 82801BA ich2 and 82801BAm ich2-m datasheet vss a22 vss aa1 vss aa2 vss aa21 vss aa22 vss ab1 vss ab2 vss ab21 vss ab22 vss b1 vss b10 vss b2 vss b21 vss b22 vss b3 vss b9 vss c2 vss c3 vss c4 vss c9 vss d3 vss d5 vss d6 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number vss l12 vss l13 vss l14 vss l9 vss m10 vss m11 vss m12 vss m13 vss m14 vss m9 vss n10 vss n11 vss n12 vss n13 vss n14 vss n9 vss p10 vss p11 vss p12 vss p13 vss p14 vss p9 table 15-1. ich2 82801BA alphabetical ball list by signal name signal name ball number pinout and package information 82801BA ich2 and 82801BAm ich2-m datasheet 15-9 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number a20gate c13 a20m# d11 ac_bitclk r19 ac_rst# v22 ac_sdin0 y22 ac_sdin1 w22 ac_sdout p21 ac_sync p19 ad0 aa4 ad1 ab4 ad2 y4 ad3 w5 ad4 w4 ad5 y5 ad6 ab3 ad7 aa5 ad8 ab5 ad9 y3 ad10 w6 ad11 w3 ad12 y6 ad13 y2 ad14 aa6 ad15 y1 ad16 v2 ad17 aa8 ad18 v1 ad19 ab8 ad20 u4 ad21 w9 ad22 u3 ad23 y9 ad24 u2 ad25 ab9 ad26 u1 ad27 w10 ad28 t4 ad29 y10 ad30 t3 ad31 aa10 agpbusy# y11 apicclk n20 apicd0 p22 apicd1 n19 batlow# u20 c/be0# aa3 c/be1# ab6 c/be2# y8 c/be3# aa9 c3_stat# / gpio21 l1 clk14 m19 clk48 p20 clk66 d4 clkrun# v21 cpuperf# b14 cpupwrgd a13 cpuslp# a12 devsel# ab7 ee_cs k4 ee_din k3 ee_dout j4 ee_shclk j3 ferr# r22 frame# v3 fs0 aa12 gmuxsel# a14 gnt0# m2 gnt1# m1 gnt2# r4 gnt3# t2 gnt4# r1 gnta# / gpio16 l2 gntb# / gnt5# / gpio17 l4 gpio7 aa11 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number pinout and package information 15-10 82801BA ich2 and 82801BAm ich2-m datasheet gpio8 y14 gpio12 w14 gpio13 ab15 gpio25 w15 gpio27 ab14 gpio28 aa14 hl_stb a6 hl_stb# a7 hl0 a4 hl1 b5 hl2 a5 hl3 b6 hl4 b7 hl5 a8 hl6 b8 hl7 a9 hl8 c8 hl9 c6 hl10 c7 hl11 c5 hlcomp a3 hubref b4 ignne# a11 init# c12 intr c11 intruder# t19 irdy# w8 irq14 f21 irq15 c16 lad0 / fwh0 y12 lad1 / fwh1 w12 lad2 / fwh2 ab13 lad3 / fwh3 ab12 lan_clk g3 lan_pwrok y16 lan_rstsync h2 lan_rxd0 g2 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number lan_rxd1 g1 lan_rxd2 h1 lan_txd0 f3 lan_txd1 f2 lan_txd2 f1 ldrq0# y13 ldrq1# w13 lframe# / fwh4 ab11 nmi b11 oc0# w19 oc1# y20 oc2# y21 oc3# w20 par w2 pciclk w11 pcirst# aa15 pda0 f20 pda1 f19 pda2 e22 pdcs1# e21 pdcs3# e19 pdd0 h19 pdd1 h22 pdd2 j19 pdd3 j22 pdd4 k21 pdd5 l20 pdd6 m21 pdd7 m22 pdd8 l22 pdd9 l21 pdd10 k22 pdd11 k20 pdd12 j21 pdd13 j20 pdd14 h21 pdd15 h20 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number pinout and package information 82801BA ich2 and 82801BAm ich2-m datasheet 15-11 pddack# f22 pddreq g22 pdior# g19 pdiow# g21 perr# y7 piordy g20 pirqa# p1 pirqb# p2 pirqc# p3 pirqd# n4 pirqe# n3 pirqf# / gpio3 n2 pirqg# / gpio4 n1 pirqh# m4 plock# aa7 pme# y15 pwrbtn# w21 pwrok r20 rcin# b13 req0# r2 req1# r3 req2# t1 req3# ab10 req4# p4 reqa# / gpio0 m3 reqb# / req5#/ gpio1 l3 ri# aa17 rsmrst# r21 rtcrst# t20 rtcx1 u22 rtcx2 t22 sda0 a16 sda1 d16 sda2 b16 sdcs1# c15 sdcs3# d15 sdd0 d18 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number sdd1 b19 sdd2 d19 sdd3 a20 sdd4 c20 sdd5 c21 sdd6 d22 sdd7 e20 sdd8 d21 sdd9 c22 sdd10 d20 sdd11 b20 sdd12 c19 sdd13 a19 sdd14 c18 sdd15 a18 sddack# b17 sddreq b18 sdior# d17 sdiow# c17 serirq n21 serr# w7 siordy a17 slp_s1# d14 slp_s3# w16 slp_s5# ab18 smbalert# / gpio11 ab17 smbclk ab16 smbdata aa16 smi# b12 smlink0 u19 smlink1 v20 spkr n22 stop# w1 stp_cpu# c14 stp_pci# a15 stpclk# c10 susclk aa18 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number pinout and package information 15-12 82801BA ich2 and 82801BAm ich2-m datasheet susstat# y17 thrm# aa13 trdy# v4 usbp0n y18 usbp0p w17 usbp1n aa19 usbp1p ab19 usbp2n y19 usbp2p w18 usbp3n aa20 usbp3p ab20 v_cpu_io d12 v_cpu_io d13 v5ref_sus v19 v5ref1 k2 v5ref2 m20 vbias t21 vcc1_8 d10 vcc1_8 d2 vcc1_8 k19 vcc1_8 l19 vcc1_8 p5 vcc1_8 v9 vcc1_8 e5 vcc3_3 e14 vcc3_3 e15 vcc3_3 e16 vcc3_3 e17 vcc3_3 e18 vcc3_3 f18 vcc3_3 g18 vcc3_3 h18 vcc3_3 j18 vcc3_3 p18 vcc3_3 r18 vcc3_3 r5 vcc3_3 t5 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number vcc3_3 u5 vcc3_3 v5 vcc3_3 v6 vcc3_3 v7 vcc3_3 v8 vcclan1_8 h5 vcclan1_8 j5 vcclan3_3 f5 vcclan3_3 g5 vccrtc u21 vccsus1_8 v14 vccsus1_8 v15 vccsus1_8 v16 vccsus3_3 t18 vccsus3_3 u18 vccsus3_3 v17 vccsus3_3 v18 vgate / vrmpwrgd b15 vss d7 vss d8 vss d9 vss e6 vss e7 vss e8 vss e9 vss j10 vss j11 vss j12 vss j13 vss j14 vss j9 vss k1 vss k10 vss k11 vss k12 vss k13 vss k14 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number pinout and package information 82801BA ich2 and 82801BAm ich2-m datasheet 15-13 vss k9 vss l10 vss l11 vss a1 vss a10 vss a2 vss a21 vss a22 vss aa1 vss aa2 vss aa21 vss aa22 vss ab1 vss ab2 vss ab21 vss ab22 vss b1 vss b10 vss b2 vss b21 vss b22 vss b3 vss b9 vss c2 vss c3 vss c4 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number vss c9 vss d3 vss d5 vss d6 vss l12 vss l13 vss l14 vss l9 vss m10 vss m11 vss m12 vss m13 vss m14 vss m9 vss n10 vss n11 vss n12 vss n13 vss n14 vss n9 vss p10 vss p11 vss p12 vss p13 vss p14 vss p9 table 15-2. ich2-m 82801BAm alphabetical ball list by signal name signal name ball number pinout and package information 15-14 82801BA ich2 and 82801BAm ich2-m datasheet 15.2 package information figure 15-3 and figure 15-4 illustrate the ich2 and ich2-m 360 ebga package. figure 15-3. ich2 / ich2-m package (top and side views) pin 1 i.d. pin 1 corner 23.00 0.10 19.50 0.20 top view 0.56 0.04 side view seating plane (see note 3) -c- 45 chamfer (4 places) 30 14.70 ref 0.127 a -a- -b- 0.127 a 14.70 ref 19.50 0.20 23.00 0.10 detail a 0.50 0.10 1.17 0.05 2.23 0.19 0.15 0.15 c pin #1 shiny 1.0 dia x 0.15 depth 6.75 0.50 x 6.75 0.50 from center line 90 au gate pin #1 corner no radius detail a (not to scale) notes: 1. all dimensions are in millimeters. 2. all dimensions and tolerances conform to ansi y14.5m - 1982. 3. primary datum (-c-) and seating plane are defined by the sperical crowns of the solder balls. 82801BA ich2 and 82801BAm ich2-m datasheet 15-15 pinout and package information figure 15-4. ich2 / ich2-m package (bottom view) pin a1 corner 1.00 bottom view a b c d e f g h j k l p r t u v y ab aa n w m 2 10 16 20 22 3 5 7 9 11 13 15 17 19 1 21 4 6 18 8 12 14 0.70 ? 0.50 s b s a c s ? 0.30 1.00 ref 1.00 ref ? 1.0 3 places 1.00 note 3 notes: 1. all dim ensions are in m illim eters. 2. all dimensions and tolerances conform to ansi y14.5m - 1982. 3. dimension is m easured at the maximum solder ball diameter. parallel to datum (-c-) on side view illustration. pinout and package information 15-16 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank. 82801BA ich2 and 82801BAm ich2-m datasheet 16-1 electrical characteristics electrical characteristics 16 note: the data provided in this chapter regarding the electrical characteristics of the ich2 component are preliminary and subject to change. 16.1 absolute maximum ratings case temperature under bias ..................................................................................... 0 c to +109 c storage temperature ............................................................................................... -55 c to +150 c voltage on any 3.3v pin with respect to ground ...............................................-0.5 to vcc + 0.3 v voltage on any 5v tolerant pin with respect to ground (v ref =5v)...............-0.5 to v ref + 0.3 v 1.8v supply voltage with respect to vss ..................................................................... -0.5 to +2.7v 3.3v supply voltage with respect to vss .................................................................... -0.5 to +4.6 v 5.0v supply voltage (vref) with respect to vss ......................................................... -0.5 to +5.5 v maximum power dissipation ....................................................................................................2. 0 w warning: stressing the device beyond the "absolute maximum ratings" may cause permanent damage. these are stress ratings only. see section 16.2 for the functional operating range of the ich2. 16.2 functional operating range all of the ac and dc characteristics specified in this document assume that the ich2 component is operating within the functional operating range given in this section. operation outside of the functional operating range is not recommended, and extended exposure outside of the functional operating range may affect component reliability. case temperature under bias .................................................................................... 0 c to +109 c 1.8v supply voltage (vcc1_8) with respect to vss......................................................1.7v to 1.9v 1.8v supply voltage (vccsus1_8) with respect to vss..................................................1.6v to 1.9v 3.3v supply voltage (vcc3_3, vccsus3_3) with respect to vss .........................3.102v to 3.498v 5v supply voltage (v5ref, v5ref_sus) with respect to vss ................................ 4.75v to 5.25v v_cpu_io voltage with respect to vss......................................................................................tbd ich2-m: 1.8v supply voltage (vcclan1_8) with respect to vss...........................1.6v to 1.9v ich2-m: 3.3v supply voltage (vcclan3_3) with respect to vss...................3.102v to 3.498v electrical characteristics 16-2 82801BA ich2 and 82801BAm ich2-m datasheet 16.3 d.c. characteristics notes: 1. 1.8v and 3.3v lan icc(max) in s0 was measured running full duplex lan test. 2. 1.8v sus icc(max) in s0 state was measured while running a test that continuously accessed pm registers. 3. 3.3v sus icc(max) in s0 state was measured running a concurrency test, in which all 4 usb ports were exercised. 4. 1.8v core and 3.3v i/o icc(max) in s0 state was measured running a test that generated a constant stream of cpu->pci writes, with an inverting pattern, causing data lines to switch on every clock. table 16-1. ich2-m power consumption measurements power plane maximum sustain supply current icc(max) s0 s1 s3 s4 s5 g3 (ich2-m) 1.8v core 300 ma 100 ma 0 0 0 3.3v i/o 410 ma 5 ma 0 0 0 1.8v lan 30 ma 23 ma 6 ma 6 ma 6 ma 3.3v lan (lan + lan connect component) 186 ma 180 ma 180 ma; 50 ma when lan connect componenplaced in reduced power mode (50 mhz clk ! 5mhz) 1.8v sus 5 ma 2ma (ich2) 1.8 ma (ich2-m) 1.8 ma 1.8 ma 1.8 ma 3.3v sus 15 ma 1.4 ma 1.4 ma 1.4 ma 1.4 ma vccrtc 4ua table 16-2. dc characteristic input signal association symbol associated signals v ih1 /v il1 (5v tolerant) pci signals: ad[31:0], c/be[3:0]#, devsel#, frame#, irdy#, trdy#, stop#, par, perr#, plock#, serr#, req[4:0]# pc/pci signals: req[a]#/gpio[0], reqb[#]/req[5]#/gpio[1] ide signals: pdd[15:0], sdd[15:0], pddreq, piordy, sddreq, siordy interrupt signals: irq[15:14], serirq, pirq[d:a]#, pirq[h]#, pirq[g:f]#/gpio[4:3], pirq[e]# legacy signals: rcin#, a20gate usb signals: oc[3:0]# . v ih2 /v il2 clock signals: clk66, clk48, clk14, lan_clk, pciclk ich2 (82801BA): gpio signals: gpio[7,6,4,3,1,0] ich2-m (82801BAm): gpio signals: gpio[7,4,3,1,0] power management signals: agpbusy# 82801BA ich2 and 82801BAm ich2-m datasheet 16-3 electrical characteristics v ih3 /v il3 lpc/fwh signals: ldrq[1:0]#, lad[3:0]/fwh[3:0] . system management signals: smbalert#/gpio[11] eeprom signals: ee_din ac?97 signals: ac_bitclk, ac_sdin[1:0], ac_sync v ih4 /v il4 clock signals: apicclk v ih5 /v il5 s mbus signals: smbclk, smbdata system management signals: intruder#, smlink[1:0] power management signals: rsmrst#, pwrok, gpio signals: gpio[28:27] v il6 /v ih6 lan signals: lan_rxd[2:0] v il7 /v ih7 processor signals: ferr#, apicd[1:0] v il8 /v ih8 hub interface signals: hl[11:0], hl_stb#, hl_stb v di / v cm / v se usb signals: usbp[1:0][p,n] v il9 /v ih9 rtcx1 table 16-3. dc input characteristics symbol parameter min. max unit notes v il1 input low voltage -0.5 0.8 v v ih1 input high voltage 2.0 v5ref + 0.5 v v il2 input low voltage -0.5 0.8 v v ih2 input high voltage 2.0 vcc3_3 + 0.5 v v il3 input low voltage -0.5 0.3vcc3_3 v v ih3 input high voltage 0.5vcc3_3 vcc3_3 + 0.5 v v il4 input low voltage -0.5 0.7 v v ih4 input high voltage 1.7 2.625 v v il5 input low voltage -0.5 0.6 v v ih5 input high voltage 2.1 vccsus3_3 + 0.5 v v il6 input low voltage -0.5 0.3vcc3_3 v v ih6 input high voltage 0.6vcc3_3 vcc3_3 + 0.5 v v il7 input low voltage -0.5 0.6 v v ih7 input high voltage 1.2 vcc3_3 + 0.5 v v il8 input low voltage -0.5 hubref - 0.15 v normal mode hubref - 0.20 enhanced mode table 16-2. dc characteristic input signal association (continued) symbol associated signals ich2 (82801BA): power management signals: pme#, pwrbtn#, ri#, rsm_pwrok, rtcrst#, thrm#, vrmpwrgd gpio signals: gpio[25:24, 13:12, 8] ich2-m (82801BAm) : power management signals: batlow#, clkrun#, pme#, pwrbtn#, ri#, lan_pwrok, rtcrst#, thrm#, vrmpwrgd/vgate gpio signals: gpio[25, 13:12, 8] electrical characteristics 16-4 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. v di = | usbpx[p] - usbpx[n] | 2. includes v di range. v ih8 input high voltage hubref + 0.15 vcc1_8 + 0.5 v normal mode hubref + 0.20 enhanced mode v di differential input sensitivity 0.2 v note 1 v cm differential common mode range 0.8 2.5 v note 2 v se single-ended receiver threshold 0.8 2.0 v v il9 input low voltage -0.5 0.10 v v ih10 input high voltage 0.40 2.0 v table 16-3. dc input characteristics symbol parameter min. max unit notes table 16-4. dc characteristic output signal association symbol associated signals v oh1 /v ol1 ide signals: pdd[15:0], sdd[15:0], pdiow#/pdstop, sdiow#/sdstop, pdior#/ pdwstb/prdmardy, sdior#/stwstb/srdmardy, pddack#, sddack#, pda[2:0], sda[2:0], pdcs[3,1]#, sdcs[3,1]# v oh2 /v ol2 processor signals: a20m#, cpupwrgd, cpuslp#, ignne#, init#, intr, nmi, smi#, stpclk# v oh3 /v ol3 pci signals: ad[31:0], c/be[3:0]#, pcirst#, gnt[4:0]#, par, devsel#, perr#, plock#, stop#, trdy#, irdy#, frame#, serr# interrupt signals: serirq, pirq[d:a]#, pirq[h]#, pirq[g:f]#/gpio[4:3], pirq[e]# v oh4 /v ol4 pci signals: gnt5#/gntb#/gpio17, gnta#/gpio16 lpc/fwh signals: lad[3:0]/fwh[3:0], lframe#/fwh[4] ac?97 signals: ac_rst#, ac_sdout, ac_sync lan signals: lan_rstsync, lan_txd[2:0] v ol5 /v oh5 smbus signals: smbclk, smbdata system management signals: smlink[1:0] interrupt signals: apicd[1:0] v ol6 /v oh6 eeprom signals: ee_cs, ee_dout, ee_shclk other signals: spkr] v ol7 /v oh7 usb signals: usbpo[p:n], usbp1[p:n] v ol8 /v oh8 hub signals: hl[11:0], hl_stb#, hl_stb ich2 (82801BA): power management signals: pme# gpio signals: gpio[21] ich2-m (82801BAm) : power management signals: pme#, c3_stat# ich2 (82801BA): power management signals: slp_s3#, slp_s5#, sus_stat#, susclk gpio signals: gpio[25:22, 20:18] ich2-m (82801BAm) : gpio signals: gpio[25] 82801BA ich2 and 82801BAm ich2-m datasheet 16-5 electrical characteristics notes: 1. the cpupwrgd, serr#, pirq[a:h], pme#, gpio22/cpuperf, apic[1:0], smbdata, smbclk and smlink[1:0] signals have an open drain driver, and the voh specification does not apply. these signals must have external pull-up resistors. table 16-5. dc output characteristics symbol parameter min. max unit i ol / i oh notes v ol1 output low voltage 0.5 v 4ma v oh1 output high voltage 2.4 v -0.4 ma v ol2 output low voltage 0.4 v 4.0 ma v oh2 output high voltage v_cpu_io - 0.13v v -0.5 ma note 1 v ol3 output low voltage 0.55 v 6 ma v oh3 output high voltage 2.4 v -2 ma note 1 v ol4 output low voltage 0.1vcc v 1.5 ma v oh4 output high voltage 0.9vcc v -0.5 ma note 1 v ol5 output low voltage 0.4 v 3.0 ma v oh5 output high voltage n/a v note 1 v ol6 output low voltage 0.4 v 4.0 ma v oh6 output high voltage vcc3_3 - 0.5 v -2.0 ma note 1 v ol7 output low voltage 0.4 v 5ma v oh7 output high voltage vcc - 0.5 v -2 ma v ol8 output low voltage 0.1(vcc1_8) v 1 ma normal mode 0.8 v 20 ma enhanced mode v oh8 output high voltage 0.9(vcc1_8) v -1 ma normal mode 1.6 v -1.5 ma enhanced mode electrical characteristics 16-6 82801BA ich2 and 82801BAm ich2-m datasheet note: includes apicclk, clk14, clk48, clk66, lan_clk and pciclk table 16-6. other dc characteristics symbol parameter min. max unit notes vbias voltage bias 0.32 0.44 v v5ref ich2 core well reference voltage 4.75 5.25 v vcc3_3 i/o buffer voltage 3.102 3.498 v vcc1_8 internal logic voltage 1.7 1.9 v hubref hub interface reference voltage 0.48(vcc1.8) 0.52(vcc1.8) v normal mode 0.64(vcc1.8) 0.70(vcc1.8) v enhanced mode v5ref_sus suspend well reference voltage 4.75 5.25 v vccsus3_3 suspend well i/o buffer voltage 3.102 3.498 v vccsus1_8 suspend well logic voltage 1.6 1.9 v vcclan3_3 (ich2-m) lan controller i/o buffer voltage 3.102 3.498 v vcclan1_8 (ich2-m) lan controller logic voltage 1.7 1.9 v vcc(rtc) battery voltage 2.0 3.6 v v it+ hysteresis input rising threshold 1.9 v applied to usbp[3:0][p:n] v it- hysteresis input falling threshold 1.3 v applied to usbp[3:0]p:n] v di differential input sensitivity 0.2 v |(usbpx+,usbpx-)| v cm differential common mode range 0.8 2.5 v includes v di v crs output signal crossover voltage 1.3 2.0 v v se single ended rcvr threshold 0.8 2.0 v i li1 input leakage current -1.0 +1.0 ua i li2 hi-z state data line leakage -10 +10 ua (0 v< v in < 3.3v) i li3 input leakage current - clock signals -100 +100 ua see note c in input capacitance - hub interface input capacitance - all other 8 12 pf f c = 1 mhz c out output capacitance 12 pf f c = 1 mhz c i/o i/o capacitance 12 pf f c = 1 mhz c l crystal load capacitance 7.5 15 pf 82801BA ich2 and 82801BAm ich2-m datasheet 16-7 electrical characteristics 16.4 a.c. characteristics table 16-7. clock timings sym parameter min max unit notes figure pci clock (pciclk) t1 period 30 33.3 ns 16-2 t2 high time 12 ns 16-2 t3 low time 12 ns 16-2 t4 rise time 3 ns 16-2 t5 fall time 3 ns 16-2 oscillator clock (osc) t6 period 67 70 ns 16-2 t7 high time 20 16-2 t8 low time 20 ns 16-2 usb clock (usbclk) f clk48 operating frequency 48 mhz t9 frequency tolerance 2500 ppm 1 t10 high time 7 ns 16-2 t11 low time 7 ns 16-2 t12 rise time 1.2 ns 16-2 t13 fall time 1.2 ns 16-2 suspend clock (susclk) f susclk operating frequency 32 khz 5 t14 high time 10 us 5 16-2 t15 low time 10 us 5 16-2 smbus clock (smbclk) f smb operating frequency 10 16 khz t18 high time 4.0 50 us 2 16-17 t19 low time 4.7 us 16-17 t20 rise time 1000 ns 16-17 t21 fall time 300 ns 16-17 i/o apic clock (apicclk) f ioap operating frequency 14.32 33.33 mhz t22 high time 12 36 ns 16-2 t23 low time 12 36 ns 16-2 t24 rise time 1.0 5.0 ns 16-2 t25 fall time 1.0 5.0 ns 16-2 electrical characteristics 16-8 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. the usbclk is a 48 mhz that expects a 40/60% duty cycle. 2. the maximum high time (t18 max) provide a simple guaranteed method for devices to detect bus idle conditions. 3. this specification includes pin-to-pin skew from the clock generator as well as board skew. 4. bitclk rise and fall times are measured from 10%vdd and 90%vdd. 5. susclk duty cycle can range from 30% minimum to 70% maximum. ac?97 clock (bitclk) f ac97 operating frequency 12.288 t26 output jitter 750 t27 high time 32.56 48.84 ns 16-2 t28 low time 32.56 48.84 ns 16-2 t29 rise time 2.0 6.0 ns 4 16-2 t30 fall time 2.0 6.0 ns 4 16-2 hub interface clock f hl operating frequency 66 t31 high time 6.0 ns 16-2 t32 low time 6.0 ns 16-2 t33 rise time 0.25 1.2 ns 16-2 t34 fall time 0.25 1.2 ns 16-2 t35 clk66 leads pciclk 1.0 4.5 3 table 16-7. clock timings (continued) sym parameter min max unit notes figure 82801BA ich2 and 82801BAm ich2-m datasheet 16-9 electrical characteristics table 16-8. pci interface timing sym parameter min max units notes figure t40 ad[31:0] valid delay 2 11 ns min: 0pf max: 50pf 16-3 t41 ad[31:0] setup time to pciclk rising 7 ns 16-4 t42 ad[31:0] hold time from pciclk rising 0 ns 16-4 t43 c/be[3:0]#, frame#, trdy#, irdy#, stop#, par, perr#, plock#, devsel# valid delay from pciclk rising 211ns min: 0pf max: 50pf 16-3 t44 c/be[3:0]#, frame#, trdy#, irdy#, stop#, par, perr#, plock#, idsel, devsel# output enable delay from pciclk rising 2ns 16-7 t45 c/be[3:0]#, frame#, trdy#, irdy#, stop#, perr#, plock#, devsel#, gnt[a:b]# float delay from pciclk rising 228ns 16-5 t46 c/be[3:0]#, frame#, trdy#, irdy#, stop#, serr#, perr#, devsel#, setup time to pciclk rising 7ns 16-4 t47 c/be[3:0]#, frame#, trdy#, irdy#, stop#, serr#, perr#, devsel#, req[a:b]# hold time from pclkin rising 0ns 16-4 t48 pcirst# low pulse width 1 ms 16-6 t49 gnt[a:b}#, gnt[5:0]# valid delay from pciclk rising 212ns t50 req[a:b]#, req[5:0]# setup timer to pciclk rising 12 ns electrical characteristics 16-10 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. iordy is internally synchronized. this timing is to guarantee recognition on the next clock. 2. piordy sample point from diox# assertion and pdiox# active pulse width is programmable from 2-5 pci clocks when the drive mode is mode 2 or greater. refer to the isp field in the ide timing register 3. piordy sample point from diox# assertion, pdiox# active pulse width and pdiox# inactive pulse width cycle time is the compatible timing when the drive mode is mode 0/1. refer to the tim0/1 field in the ide timing register. 4. pdiox# inactive pulse width is programmable from 1-4 pci clocks when the drive mode is mode 2 or greater. refer to the rct field in the ide timing register. table 16-9. ide pio & multiword dma mode timing sym parameter min max units notes figure t60 pdior#/pdiow#/sdior#/sdiow# active from clk66 rising 220ns 16-8 , 16-9 t61 pdior#/pdiow#/sdior#/sdiow# inactive from clk66 rising 220ns 16-8 , 16-9 t62 pda[2:0]/sda[2:0] valid delay from clk66 rising 2 30 ns 16-8 t63 pdcs1#/sdcs1#, pdcs3#/sdcs3# active from clk66 rising 230ns 16-8 t64 pdcs1#/sdcs1#, pdcs3#/sdcs3# inactive from clk66 rising 230ns 16-8 t65 pddack#/sddack# active from clk66 rising 2 20 ns 16-9 t66 pddack#/sddack# inactive from clk66 rising 2 20 ns t67 pddreq/sddreq setup time to clk66 rising 7 ns 16-9 t68 pddreq/sddreq hold from clk66 rising 7 ns 16-9 t69 pdd[15:0]/sdd[15:0] valid delay from clk66 rising 230ns 16-8 , 16-9 t70 pdd[15:0]/sdd[15:0] setup time to clk66 rising 10 ns 16-8 , 16-9 t71 pdd[15:0]/sdd[15:0] hold from clk66 rising 7 ns 16-8 , 16-9 t72 piordy/siordy setup time to clk66 rising 7 ns 1 16-8 t73 piordy/siordy hold from clk66 rising 7 ns 1 16-8 t74 piordy/siordy inactive pulse width 48 ns 16-8 t75 pdior#/pdiow#/sdior#/sdiow# pulse width low 2,3 16-8 , 16-9 t76 pdior#/pdiow#/sdior#/sdiow# pulse width high 3,4 16-8 , 16-9 82801BA ich2 and 82801BAm ich2-m datasheet 16-11 electrical characteristics note: 1. the specification symbols in parentheses correspond to the ultra ata specification name. table 16-10. ultra ata timing (mode 0, mode 1, mode 2) sym parameter (1) mode 0 (ns) mode 1 (ns) mode 2 (ns) figure min max min max min max t80 sustained cycle time (t2cyctyp) 240 160 120 t81 cycle time (tcyc) 112 73 54 16-11 t82 two cycle time (t2cyc) 230 154 115 16-11 t83 data setup time (tds) 15 10 7 16-11 t84 data hold time (tdh) 5 5 5 16-11 t85 data valid setup time (tdvs) 70 48 30 16-11 t86 data valid hold time (tdvh) 6 6 6 16-11 t87 limited interlock time (tli) 0 150 0 150 0 150 16-13 t88 interlock time w/ minimum (tmli) 20 20 20 16-13 t89 envelope time (tenv) 20 70 20 70 20 70 16-10 t90 ready to pause time (trp) 160 125 100 16-12 t91 dmack setup/hold time (tack) 20 20 20 16-10 , 16-13 table 16-11. ultra ata timing (mode 3, mode 4, mode 5) sym parameter (1) mode 3 (ns) mode 4 (ns) mode 5 (ns) figure min max min max min max t80 sustained cycle time (t2cyctyp) 90 60 40 t81 cycle time (tcyc) (2) 39 25 16.8 16-11 t82 two cycle time (t2cyc) 86 57 38 16-11 t83 data setup time (tds) 7 5 4.0 16-11 t84 data hold time (tdh) 5 5 4.6 16-11 t85 data valid setup time (tdvs) 20 6 3.3 16-11 t86 data valid hold time (tdvh) 6 6 3.3 16-11 t87 limited interlock time (tli) 0 100 0 100 0 75 16-13 t88 interlock time w/ minimum (tmli) 20 20 20 16-13 t89 envelope time (tenv) 20 55 20 55 20 50 16-10 t90 ready to pause time (trp) 100 100 85 16-12 t91 dmack setup/hold time (tack) 20 20 20 16-10 , 16-13 electrical characteristics 16-12 82801BA ich2 and 82801BAm ich2-m datasheet notes: 1. driver output resistance under steady state drive is specified at 28 ohms at minimum and 43 ohms at maximum 2. timing difference between the differential data signals 3. measured at crossover point of differential data signals 4. measured at 50% swing point of data signals 5. measured from last crossover point to 50% swing point of data line at leading edge of eop 6. measured from 10% to 90% of the data signal 7. full speed data rate has minimum of 11.97 mbps and maximum of 12.03 mbps 8. low speed data rate has a minimum of 1.48 mbps and a maximum of 1.52 mbps table 16-12. universal serial bus timing sym parameter min max units notes fig full speed source (note 7) t100 usbpx+, usbpx- driver rise time 4 20 ns 1, c l = 50 pf 16-14 t101 usbpx+, usbpx- driver fall time 4 20 ns 1, c l = 50 pf 16-14 t102 source differential driver jitter to next transition for paired transitions -2 -1 2 1 ns ns 2, 3 16-15 t103 source eop width 160 175 ns 4 16-16 t104 differential to se0 transition skew -2 5 ns 5 t105 receiver data jitter tolerance to next transition for paired transitions -20 -10 20 10 ns ns 3 16-15 t106 eop width: must reject as eop eop width: must accept as eop 40 85 ns ns 4 16-16 t107 differential to se0 transition skew -2 5 ns 5 low speed source (note 8) t108 usbpx+, usbpx- driver rise time 75 300 ns ns 1, 6 c l = 50 pf c l = 350 pf 16-14 t109 usbpx+, usbpx- driver fall time 75 300 ns ns 1,6 c l = 50 pf c l = 350 pf 16-14 t110 source differential driver jitter to next transition for paired transitions -2 -1 2 1 ns ns 2, 3 16-15 t111 source eop width 160 175 ns 4 16-16 t112 differential to se0 transition skew -2 5 ns 5 t113 receiver data jitter tolerance to next transition for paired transitions -20 -10 20 10 ns ns 3 16-15 t114 eop width: must reject as eop eop width: must accept as eop 40 85 ns ns 4 16-16 t115 differential to se0 transition skew -2 5 ns 5 82801BA ich2 and 82801BAm ich2-m datasheet 16-13 electrical characteristics notes: 1. a device will time out when any clock low exceeds this value. 2. t137 is the cumulative time a slave device is allowed to extend the clock cycles in one message from the initial start to stop. if a slave device exceeds this time, it is expected to release both its clock and data lines and reset itself. 3. t138 is the cumulative time a master device is allowed to extend its clock cycles within each byte of a message as defined from start-to-ack, ack-to-ack or ack-to-stop. table 16-13. ioapic bus timing sym parameter min max units notes fig t120 apiccd[1:0]# valid delay from apicclk rising 3.0 12.0 ns 16-3 t121 apiccd[1:0]# setup time to apicclk rising 8.5 ns 16-4 t122 apiccd[1:0]# hold time from apicclk rising 3.0 ns 16-4 table 16-14. smbus timing sym parameter min max units notes fig t130 bus tree time between stop and start condition 4.7 us 16-17 t131 hold time after (repeated) start condition. after this period, the first clock is generated. 4.0 us 16-17 t132 repeated start condition setup time 4.7 us 16-17 t133 stop condition setup time 4.0 us 16-17 t134 data hold time 300 ns 16-17 t135 data setup time 250 ns 16-17 t136 device time out 25 35 ms 1 t137 cumulative clock low extend time (slave device) 25 ms 2 16-18 t138 cumulative clock low extend time (master device) 10 ms 3 16-18 table 16-15. ac?97 timing sym parameter min max units notes fig t140 acsdin[0:1] setup to falling edge of bitclk 15 ns t141 acsdin[0:1] hold from falling edge of bitclk 5 ns t142 acsync, acsdout valid delay from rising edge of bitclk 15 ns 16-3 electrical characteristics 16-14 82801BA ich2 and 82801BAm ich2-m datasheet table 16-16. lpc timing sym parameter min max units notes fig t150 lad[3:0] valid delay from pciclk rising 2 11 ns 16-3 t151 lad[3:0] output enable delay from pciclk rising 2 ns 16-7 t152 lad[3:0] float delay from pciclk rising 28 ns 16-5 t153 lad[3:0] setup time to pciclk rising 7 ns 16-4 t154 lad[3:0] hold time from pciclk rising 0 ns 16-4 t155 ldrq[1:0]# setup time to pciclk rising 12 ns 16-4 t156 ldrq[1:0]# hold time from pciclk rising 0 ns 16-4 t157 lframe# valid delay from pciclk rising 2 12 ns 16-3 table 16-17. miscellaneous timings sym parameter min max units notes fig t160 serirq setup time to pciclk rising 7 ns 16-4 t161 serirq hold time from pciclk rising 0 ns 16-4 t162 ri#, extsmi#, gpi, usb resume pulse width 2 rtcclk 16-6 t163 spkr valid delay from osc rising 200 ns 16-3 t164 serr# active to nmi active 200 ns t165 ignne# inactive from ferr# inactive 230 ns table 16-18. power sequencing and reset signal timings sym parameter min max units notes fig t170 vccrtc active to rtcrst# inactive 5 - ms 16-18 , 16-19 t171 v5refsus active to vccsus3_3, vccsus1_8 active 0- ms1, 2 16-18 , 16-19 t172 vccrtc supply active to vccsus supplies active 0- ms3 16-18 , 16-19 t173 (ich2) vccsus supplies active to rsm_pwrok active, rsmrst# inactive 10 - ms 16-18 , 16-21 t173 (ich2-m) vccsus supplies active to rsmrst# inactive 5 - ms 16-19 16-22 t174 v5ref active to vcc3_3, vcc1_8 active 0 - ms 1, 2 16-18 , 16-19 t175 (ich2) vccsus supplies active to vcc supplies active 0 - ms 3 16-18 t175a (ich2-m) vccsus supplies active to vcclan supplies active 0 - ms 3 16-19 t175b (ich2-m) vcclan supplies active to lan_pwrok active 10 - ms 16-19 16-20 t175c (ich2-m) vcclan supplies active to vcc supplies active 0 - ms 16-19 82801BA ich2 and 82801BAm ich2-m datasheet 16-15 electrical characteristics notes: 1. the v5ref supply must power up before or simultaneous with its associated 3.3v supply, and must power down simultaneous with or after the 3.3v supply. see section 2.20.4 for details. 2. the associated 3.3v and 1.8v supplies are assumed to power up or down together. the difference between the levels of the 3.3v and 1.8v supplies must never be greater than 2.0v. t176 (ich2) vcc supplies active to pwrok, vrmpwrgd active 10 - ms 16-18 , 16-21 , 16-25 t176 (ich2-m) vcc supplies active to pwrok, vgate active 10 - ms 16-19 16-20 16-22 t177 pwrok, vrmpwrgd active to sus_stat# inactive 32 34 rtcclk 16-18 , 16-21 16-25 t177 pwrok, vgate active to sus_stat# inactive 32 34 rtcclk 16-18 16-20 16-22 t178 sus_stat# inactive to pcirst# inactive 1 3 rtcclk 16-18 , 16-19 16-21 , 16-22 16-25 , 16-26 t179 ac_rst# active low pulse width 1 us t180 ac_rst# inactive to bit_clk startup delay 162.8 ns table 16-18. power sequencing and reset signal timings (continued) sym parameter min max units notes fig 3. 82801BA ich2: the vccsus supplies must never be active while the vccrtc supply is inactive. likewise, the vcc supplies must never be active while the vccsus supplies are inactive. 4. 82801BAm ich2-m: the vccsus supplies must never be active while the vccrtc supply is inactive. likewise, the vcc or vcclan supplies must never be active while the vccsus supplies are inactive, and the vcc supplies must never be active while the vcclan supplies are inactive. electrical characteristics 16-16 82801BA ich2 and 82801BAm ich2-m datasheet table 16-19. power management timings sym parameter min max units notes fig t181 vccsus active to slp_s3#, slp_s5#, sus_stat# and pcirst# active 50 ns 16-21 , 16-22 t182 t183 rsmrst# inactive to susclk running, slp_s3#, slp_s5# inactive 110 ms 7 16-21 , 16-22 t184 (ich2) vcc active to stpclk#, cpuslp#, inactive, and processor frequency strap signals high 50 ns 16-21 , 16-25 t184 (ich2-m) vcc active to stpclk#, cpuslp#, stp_cpu#, stp_pci#, slp_s1, c3_stat# inactive, and cpu frequency strap signals high 50 ns 16-20 16-22 t185 pwrok and vrmpwrgd active to sus_stat# inactive and processor frequency straps latched to strap values 32 34 rtcclk 1 16-21 , 16-22 t186 processor reset complete to frequency strap signals unlatched from strap values 79clk662 16-21 , 16-22 t187 stpclk# active to stop grant cycle n/a n/a 3 16-23 , 16-24 16-25 , 16-26 t188 (ich2) stop grant cycle to cpuslp# active 60 63 pciclk 4 16-25 , 16-25 t188a (ich2-m) stop grant cycle to c3_stat# active 0 6 pciclk 4 16-23 , 16-26 , 16-28 t188b (ich2-m) c3_stat# active to cpuslp# active 2.8 u s 16-23 , 16-26 , 16-28 t189 (ich2) s1 wake event to cpuslp# inactive 1 25 pciclk 4 16-23 t190 cpuslp# inactive to stpclk# inactive 204 237 u s 16-23 , 16-25 t192 (ich2) cpuslp# active to sus_stat# active 2 4 rtcclk 1 16-25 t192a (ich2-m) cpuslp# active to stp_cpu# active 16 pciclk 4 16-23 , 16-26 , 16-28 t192b (ich2-m) stp_cpu# active to sus_stat# active 2 4 rtcclk 1 16-23 , 16-26 , t193 (ich2) sus_stat# active to pcirst# active 9 15 rtcclk 1 16-25 t193a (ich2-m) sus_stat# active to stp_pci# active 2 4 rtcclk 1 16-23 , 16-26 , t193b (ich2-m) stp_pci# active to slp_s1# active 2 4 rtcclk 1 16-23 , 16-26 , t193c (ich2-m) slp_s1# active to pcirst# active, stp_pci# inactive, slp_s1# inactive, and stp_cpu# inactive 5 7 rtcclk 1 16-23 , 16-26 , t194 pcirst# active to slp_s3# active 1 2 rtcclk 1 16-25 , 16-26 82801BA ich2 and 82801BAm ich2-m datasheet 16-17 electrical characteristics notes: 1. these transitions are clocked off the internal rtc. one rtc clock is approximately 32 us. 2. this transition is clocked off the 66 mhz clk66. one clk66 is approximately 15 ns. 3. the ich2 stpclk# assertion will trigger the processor to send a stop grant acknowledge cycle. the timing for this cycle getting to the ich2 is dependant on the processor and the memory controller. 4. these transitions are clocked off the 33 mhz pciclk. 1 pciclk is approximately 30 ns. 5. the ich2 has no maximum timing requirement for this transition. it is up to the system designer to determine if the slp_s3# and slp_s5# signals are used to control the power planes. 6. if the transition to s5 is due to power button override, slp_s3# and slp_s5# are asserted together following timing t194 (pcirst# active to slp_s3# and slp_s5# active). 7. if there is no rtc battery in the system, so vccrtc and the vccsus supplies come up together, the delay from rtcrst# and rsmrst# inactive to susclk toggling may be as much as 1000 ms. t195 slp_s3# active to slp_s5# active 1 2 rtcclk 1, 6 16-25 , 16-26 t196 slp_s3# active to vrmpwrgd (vrmpwrgd / vgate for ich2-m) inactive 0ms5 16-25 , 16-26 t196a slp_s3# active to pwrok 100 us 16-25 , 16-26 t197 pwrok, vrmpwrgd inactive to vcc supplies inactive 20 ns 16-25 , 16-26 t198 wake event to slp_s3#, slp_s5# inactive 1 20 rtcclk 1 16-25 , 16-26 t198a (ich2-m) wake event to slp_s1# inactive 1 20 rtcclk 1 16-23 , t199 (ich2-m) slp_s1# inactive to stp_cpu#, stp_pci# inactive 3 6 ms 16-23 , t200 (ich2-m) stp_cpu#, stp_pci# inactive to sus_stat# inactive 7 10 ms 16-23 , t201 (ich2-m) sus_stat# inactive to cpu_slp# inactive 2 4 pciclk 4 16-23 , t203 (ich2-m) stpclk# inactive to c3_stat# inactive 0 15 ns 16-23 , 16-28 t204 processor i/f signals latched prior to stpclk# active 04clk662 16-27 t205 break event to stpclk# inactive 30 3120 ns 16-27 t206 stpclk# inactive to processor i/f signals unlatched 240 1880 ns 16-27 t207 (ich2-m) break event to stp_cpu# inactive 0 8 pciclk 4 16-28 t208 (ich2-m) stp_cpu# inactive to cpu_slp# inactive 30 45 u s 16-28 table 16-19. power management timings sym parameter min max units notes fig electrical characteristics 16-18 82801BA ich2 and 82801BAm ich2-m datasheet 16.5 timing diagrams figure 16-1. clock timing figure 16-2. valid delay from rising clock edge figure 16-3. setup and hold times figure 16-4. float delay 2.0v 0.8v period high time low time fall time rise time clock 1.5v valid delay vt output clock vt input hold time setup time vt 1.5v input vt output float delay 82801BA ich2 and 82801BAm ich2-m datasheet 16-19 electrical characteristics figure 16-5. pulse width figure 16-6. output enable delay figure 16-7. ide pio mode vt pulse width vt clock output output enable delay vt 1.5v t62,t63 t64 da[2:0], cs1#, cs3# t75 t69 t69 t70 t71 t72 t73 t61 read data clk66 diox# dd[15:0] write dd[15:0] read iordy t60 t76 write data sample point t74 electrical characteristics 16-20 82801BA ich2 and 82801BAm ich2-m datasheet figure 16-8. ide multiword dma figure 16-9. ultra ata mode (drive initiating a burst read) clk66 id d d t67 ddreq[1:0] ddack[1:0] t65 diox# dd[15:0] read dd[15:0] write t60 t61 t75 t76 t70 t71 t69 t69 read data write data write data read data t68 dmarq (drive) t91 t89 t89 dmack# (host) stop (host) dmardy# (host) strobe (drive) dd[15:0] da[2:0], cs[1:0] 82801BA ich2 and 82801BAm ich2-m datasheet 16-21 electrical characteristics figure 16-10. ultra ata mode (sustained burst) figure 16-11. ultra ata mode (pausing a dma burst) strobe @ sender t81 data @ sender t86 t85 t86 t85 t81 t82 t86 strobe @ receiver data @ receiver t84 t83 t84 t83 t84 t90 strobe data stop (host) dmardy# electrical characteristics 16-22 82801BA ich2 and 82801BAm ich2-m datasheet figure 16-12. ultra ata mode (terminating a dma burst) figure 16-13. usb rise and fall times figure 16-14. usb jitter t88 stop (host) strobe (host) dmardy# (drive) data (host) dmack# (host) t91 t87 dmarq (drive) crc full speed: 4 to 20 ns at c l = 50 pf differential data lines 90% 10% 10% 90% tr tf rise time fall time low speed: 75 ns at c l = 50 pf, 300 ns at c l = 350 pf c l c l differential data lines consecutive transitions paired transitions crossover points tperiod 82801BA ich2 and 82801BAm ich2-m datasheet 16-23 electrical characteristics figure 16-15. usb eop width figure 16-16. smbus transaction figure 16-17. smbus time-out differential data lines eop width data crossover level tperiod t130 smbclk smbdata t131 t19 t134 t20 t21 t135 t132 t18 t133 start stop t137 clk ack clk ack t138 t138 smbclk smbdata electrical characteristics 16-24 82801BA ich2 and 82801BAm ich2-m datasheet figure 16-18. power sequencing and reset signal timings (82801BA ich2 only) figure 16-19. power sequencing and reset signal timings (82801BAm ich2-m only) vccrtc v5ref vcc3_3, vcc1_8, v_cpu_io vccsus3_3, vccsus1_8 v5refsus rtcrst# rsmrst#, rsm_pwrok pwrok, vrmpwrgd t170 t171 t172 t173 t174 t175 t176 ich2_powerup_reset_dt.vsd vccrtc vccsus3_3, vccsus1_8 v5refsus rtcrst# rsmrst# t170 t171 t172 t173 t174 t176 pwrok, vgate vcc3_3, vcc1_8, v_cpu_io v5ref vcclan3_3, vcclan1_8 lan_pwrok t175a t175b t175c ich2_powerup_reset_mo.vst 82801BA ich2 and 82801BAm ich2-m datasheet 16-25 electrical characteristics figure 16-20. 1.8v/3.3v power sequencing figure 16-21. g3 (mechanical off) to s0 timings (82801BA ich2 only) t time 1.8 3.3 v v v < 2.0v voltage s2 vccsus running susclk slp_s3# slp_s5# vcc pwrok, vrmpwrgd sus_stat# pcirst# frequency straps stpclk#, cpuslp# strap values normal operation hub interface "cpu reset complete" message rsmrst#, rsm_pwrok t173 t176 t177 t178 t181 t181 t182 t183 t184 t185 t186 g3 s5 s0 s0 state ich2_g3_s0_timing_dt1.vst g3 s5 system state electrical characteristics 16-26 82801BA ich2 and 82801BAm ich2-m datasheet figure 16-22. g3 (mechanical off) to s0 timings (82801BAm ich2-m only) figure 16-23. s0 to s1 to s0 timings (82801BA ich2 only) vccsus running susclk slp_s3# slp_s5# vcc, vcclan pwrok, vgate, lan_pwrok sus_stat# pcirst# frequency straps stpclk#, cpuslp#, stp_cpu#, stp_pci#, slp_s1#, c3_stat# strap values normal operation hub interface "cpu reset complete" message rsmrst# t173 t175b / t176 t177 t178 t181 t181 t182 t183 t184 t185 t186 main battery removed (g3) s5 s0 s0 state ich2 g3 s0 timing mo vsd g3 s5 system state t187 t188 t189 t190 ich2_s0_s1d_timing.vsd s0 s0 s1 s1 s1 s0 s0 state stpclk# pci stop grant cycle cpuslp# wake event 82801BA ich2 and 82801BAm ich2-m datasheet 16-27 electrical characteristics figure 16-24. s0 to s1 to s0 timings (82801BAm ich2-m only) figure 16-25. s0 to s5 to s0 timings (82801BA ich2 only) state stpclk# pci stop grant cycle cpuslp# wake event slp_s1# c3_stat# stp_cpu# sus_stat# stp_pci# s0 s0 s1 s1 s1 s0 s0 t187 t198a t188a t188b t192a t192b t193a t193b t199 t200 t201 t190 t203 slp_s3# slp_s5# wake event vcc s0 s0 s3 s3 s4/s5 s3/s4/s5 s0 s0 t195 t197 t198 t177 t178 t184 stpclk# stop grant cycle t187 t188 t192 t194 t193 cpuslp# sus_stat# pcirst# vrmpwrgd t196 t176 pwrok t196a t176 electrical characteristics 16-28 82801BA ich2 and 82801BAm ich2-m datasheet figure 16-26. s0 to s5 to s0 timings (82801BAm ich2-m only) figure 16-27. c0 to c2 to c0 timings cpuslp# sus_stat# pcirst# slp_s3# slp_s5# w ake event vgate vcc s0 s0 s3 s3 s4/s5 s3/s4/s5 s0 s0 t195 t196 t197 t198 t176 t177 t178 t184 slp_s1# stpclk# stop grant cycle c3_stat# stp_cpu# t187 t188a t188b t192a t192b t193a t193b t194 t193c stp_pci# t196a t176 pwrok unlatched latched unlatched cpu i/f signals stpclk# break event ich2 c0 c2 ti i d t204 t205 t206 82801BA ich2 and 82801BAm ich2-m datasheet 16-29 electrical characteristics figure 16-28. c0 to c3 to c0 timings (82801BAm ich2-m only) unlatched latched unlatched cpu i/f signals stpclk# ich2_c0_c3_timing.vsd break event pci stop grant cycle c3_stat# cpu_slp# stp_cpu# t204 t188a t188b t192a t207 t208 t190 t206 t203 electrical characteristics 16-30 82801BA ich2 and 82801BAm ich2-m datasheet this page is intentionally left blank. 82801BA ich2 and 82801BAm ich2-m datasheet 17-1 testability testability 17 17.1 test mode description the ich2 supports two types of test modes, a tri-state test mode and a xor chain test mode. driving rtcrst# low for a specific number of pci clocks while pwrok is high activates a particular test mode as described in table 17-1 . note: rtcrst# can be driven low any time after pcirst# is inactive. . figure 17-1 illustrates the entry into a test mode. a particular test mode is entered upon the rising edge of the rtcrst# after being asserted for a specific number of pci clocks while pwrok is active. to change test modes, the same sequence should be followed again. to restore the ich2 to normal operation, execute the sequence with rtcrst# being asserted so that no test mode is selected as specified in table 17-1 . table 17-1. test mode selection number of pci clocks rtcrst# driven low after pwrok active test mode <4 no test mode selected 4 xor chain 1 5 xor chain 2 6 xor chain 3 7 xor chain 4 8all ?z? 9 - 24 reserved. do not attempt >24 no test mode selected figure 17-1. test mode entry (xor chain example) rsmrst# pwrok rtcrst# other signal outputs n number of pci clocks test mode entered all output signals tri-stated xor chain output enabled testability 17-2 82801BA ich2 and 82801BAm ich2-m datasheet 17.2 tri-state mode when in the tri-state mode, all outputs and bi-directional pin are tri-stated, including the xor chain outputs. 17.3 xor chain mode in the ich2, provisions for automated test equipment (ate) board level testing are implemented with xor chains. the ich2 signals are grouped into four independent xor chains which are enabled individually. when an xor chain is enabled, all output and bi-directional buffers within that chain are tri-stated, except for the xor chain output. every signal in the enabled xor chain (except for the xor chain?s output) functions as an input. all output and bi-directional buffers for pins not in the selected xor chain are tri-stated. figure 17-2 is a schematic example of xor chain circuitry. table 17-3 - table 17-6 list each xor chain pin ordering, with the first value being the first input and the last value being the xor chain output. table 17-7 lists the signal pins not included in any xor chain. 17.3.1 xor chain testability algorithm example xor chain testing allows motherboard manufacturers to check component connectivity (e.g., opens and shorts to vcc or gnd). an example algorithm to do this is shown in table 17-2 . figure 17-2. example xor chain circuitry input pin 2 vcc input pin 1 input pin 3 input pin 4 input pin 5 input pin 6 xor chain output table 17-2. xor test pattern example vector input pin 1 input pin 2 input pin 3 input pin 4 input pin 5 input pin 6 xor output 10000001 21000000 31100001 41110000 51111001 61111100 71111111 82801BA ich2 and 82801BAm ich2-m datasheet 17-3 testability in this example, vector 1 applies all "0s" to the chain inputs. the outputs being non-inverting, will consistently produce a "1" at the xor output on a good board. one short to vcc (or open floating to vcc) will result in a "0" at the chain output, signaling a defect. likewise, applying vector 7 (all "1s") to the chain inputs (given that there are an even number of input signals in the chain), will consistently produce a "1" at the xor chain output on a good board. one short to vss (or open floating to vss) will result in a "0" at the chain output, signaling a defect. it is important to note that the number of inputs pulled to "1" will affect the expected chain output value. if the number of chain inputs pulled to "1" is even, then expect "1" at the output. if the number of chain inputs pulled to "1" is odd, expect "0" at the output. continuing with the example in table 17-2 , as the input pins are driven to "1" across the chain in sequence, the xor output will toggle between "0" and "1." any break in the toggling sequence (e.g., "1011") will identify the location of the short or open. 17.3.1.1 test pattern consideration for xor chain 4 when the ich2 is operated with the hub interface in "normal" mode (see section 2.20.1 ), the hl_stb and hl_stb# signals must always be driven to complementary logic levels. for example, if a "1" is driven on hl_stb, then a "0" must be driven on hl_stb# and vice versa. this will need to be considered in applying test patterns to this chain. when the ich2 is operated with the hub interface in "enhanced" mode there are no restrictions on the values that may be driven onto the hl_stb and hl_stb# signals. testability 17-4 82801BA ich2 and 82801BAm ich2-m datasheet table 17-3. xor chain #1 (rtcrst# asserted for 4 pci clocks while pwrok active) pin name ball # notes pin name ball # notes lan_txd0 f3 top of xor chain req2# t1 lan_txd1 f2 2nd signal in xor gnt2# r4 lan_txd2 f1 gnt3# t2 lan_rxd0 g2 ad26 u1 lan_rxd1 g1 ad30 t3 lan_rxd2 h1 ad28 t4 ee_dout j4 ad18 v1 ee_shclk j3 ad22 u3 ee_cs k4 ad16 v2 ee_din k3 stop# w1 gpio21 (ich2) c3_stat#/ gpio21 (ich2-m) l1 par w2 gpio16 / gnta# l2 frame# v3 gpio1 / reqb# / req5# l3 ad20 u4 gpio17 / gntb# / gnt5# l4 ad15 y1 gnt1# m1 trdy# v4 gnt0# m2 ad11 w3 gpio0 / reqa# m3 ad13 y2 pirqh# m4 ad4 w4 gpio4 / pirqg# n1 ad9 y3 gpio3 / pirqf# n2 c/be0# aa3 pirqe# n3 ad2 y4 pirqd# n4 ad6 ab3 pirqa# p1 ad3 w5 pirqb# p2 ad0 aa4 pirqc# p3 ad5 y5 req4# p4 ad10 w6 gnt4# r1 ad7 aa5 last in xor chain req0# r2 xor chain #1 req1# r3 ac_sdin1 w22 output 82801BA ich2 and 82801BAm ich2-m datasheet 17-5 testability table 17-4. xor chain #2 (rtcrst# asserted for 5 pci clocks while pwrok active) pin name ball # notes pin name ball # notes ad1 ab4 top of xor chain ldrq1# w13 ad12 y6 2nd signal in xor gpio27 ab14 ad8 ab5 gpio28 aa14 serr# w7 gpio8 y14 ad14 aa6 gpio12 w14 perr# y7 gpio13 ab15 c/be1# ab6 pcirst# aa15 devsel# ab7 pme# y15 plock# aa7 gpio25 w15 c/be2# y8 smbclk ab16 irdy# w8 smbdata aa16 ad17 aa8 smbalert# / gpio11 ab17 ad19 ab8 ri# aa17 ad23 y9 slp_s5# ab18 ad21 w9 susstat# y17 c/be3# aa9 slp_s3# w16 ad25 ab9 susclk aa18 ad27 w10 usbp0p w17 ad29 y10 usbp0n y18 ad31 aa10 usbp1p ab19 req3# ab10 usbp1n aa19 gpio6 (ich2) agpbusy# (ich2-m) y11 usbp2p w18 gpio7 aa11 usbp2n y19 lframe# / fwh4 ab11 usbp3p ab20 lad3 / fwh3 ab12 usbp3n aa20 fs0 aa12 oc0# w19 lad0 / fwh0 y12 oc1# y20 lad1 / fwh1 w12 oc2# y21 lad2 / fwh2 ab13 oc3# w20 thrm# aa13 xor chain #2 ldrq0# y13 tp0 (ich2) batlow# (ich2-m) u20 output testability 17-6 82801BA ich2 and 82801BAm ich2-m datasheet table 17-5. xor chain #3 (rtcrst# asserted for 6 pci clocks while pwrok active) pin name ball # notes pin name ball # notes ac_sdin0 y22 top of xor chain pdd14 h21 pwrbtn# w21 2nd signal in xor pdd0 h19 smlink0 u19 pddreq g22 smlink1 v20 pdiow# g21 ac_sdin1 w22 pdd15 h20 tp0 (ich2) batlow# (ich2-m) u20 pddack# f22 ac_rst# v22 pda2 e22 gpio24 (ich2) clkrun# (ich2-m) v21 irq14 f21 ac_sdout p21 sdd6 d22 ac_sync p19 piordy g20 ferr# r22 pdcs1# e21 apicd0 p22 pdior# g19 apicd1 n19 pda0 f20 serirq n21 sdd8 d21 spkr n22 sdd9 c22 pdd6 m21 pda1 f19 pdd7 m22 sdd7 e20 pdd8 l22 sdd5 c21 pdd9 l21 sdd10 d20 pdd5 l20 sdd4 c20 pdd10 k22 pdcs3# e19 pdd4 k21 sdd11 b20 pdd11 k20 sdd2 d19 pdd13 j20 sdd12 c19 pdd3 j22 sdd3 a20 last in xor chain pdd12 j21 xor chain #3 pdd1 h22 ri# aa17 output pdd2 j19 82801BA ich2 and 82801BAm ich2-m datasheet 17-7 testability table 17-6. xor chain #4 (rtcrst# asserted for 7 pci clocks while pwrok active) pin name ball # notes pin name ball # notes sdd13 a19 top of xor chain init# c12 sdd1 b19 2nd signal in xor smi# b12 sdd14 c18 cpuslp# a12 sdd0 d18 ignne# a11 sdior# d17 nmi b11 sddreq b18 intr c11 sdiow# c17 a20m# d11 sdd15 a18 stpclk# c10 sda1 d16 hl7 a9 sddack# b17 hl5 a8 irq15 c16 hl6 b8 siordy a17 hl4 b7 sda2 b16 hl8 c8 sdcs3# d15 hl10 c7 see section 17.3.1.1 sda0 a16 hl_stb# a7 see section 17.3.1.1 sdcs1# c15 hl_stb a6 vrmpwrgd (ich2) vrmpwrgd / vgate (ich2-m) b15 hl9 c6 gpio18 (ich2) stp_pci# (ich2-m) a15 hl2 a5 gpio19 (ich2) slp_s1# (ich2-m) d14 hl1 b5 gpio20 (ich2) stp_cpu# (ich2-m) c14 hl0 a4 gpio22 (ich2) cpuperf# (ich2-m) b14 hl11 c5 gpio23 (ich2) ssmuxsel# (ich2-m) a14 hlcomp a3 last in xor chain a20gate c13 xor chain #4 rcin# b13 oc0# w19 output cpupwrgd a13 testability 17-8 82801BA ich2 and 82801BAm ich2-m datasheet table 17-7. signals not in xor chain pin name ball # notes pin name ball # notes rsmrst# r21 clk14 m19 pwrok r20 clk48 p20 rtcx1 u22 clk66 d4 rtcx2 t22 apicclk n20 vbias t21 pciclk w11 rtcrst# t20 intruder# t19 lan_clk g3 rsm_pwrok (ich2) lan_pwrok (ich2-m) y16 ac_bitclk r19 82801BA ich2 and 82801BAm ich2-m datasheet a-1 i/o register index i/o register index a table a-1. ich2 fixed i/o registers register name port eds section and location channel 0 dma base & current address register 00h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 channel 0 dma base & current count register 01h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 channel 1 dma base & current address register 02h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 channel 1 dma base & current count register 03h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 channel 2 dma base & current address register 04h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 channel 2 dma base & current count register 05h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 channel 3 dma base & current address register 06h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 channel 3 dma base & current count register 07h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 channel 0?3 dma command register channel 0?3 dma status register 08h section 9.2.4, ?dmacmd?dma command register? on page 9-26 section 9.2.5, ?dmasts?dma status register? on page 9-26 channel 0?3 dma write single mask register 0ah section 9.2.6, ?dma_wrsmsk?dma write single mask register? on page 9-27 channel 0?3 dma channel mode register 0bh section 9.2.7, ?dmach_mode?dma channel mode register? on page 9-27 channel 0?3 dma clear byte pointer register 0ch section 9.2.8, ?dma clear byte pointer register? on page 9-28 channel 0?3 dma master clear register 0dh section 9.2.9, ?dma master clear register? on page 9-28 channel 0?3 dma clear mask register 0eh section 9.2.10, ?dma_clmsk?dma clear mask register? on page 9-28 channel 0?3 dma write all mask register 0fh section 9.2.11, ?dma_wrmsk?dma write all mask register? on page 9-29 aliased at 00h?0fh 10h?1fh master pic icw1 init. cmd word 1 register master pic ocw2 op ctrl word 2 register master pic ocw3 op ctrl word 3 register 20h section 9.4.2, ?icw1?initialization command word 1 register? on page 9-34 section 9.4.8, ?ocw2?operational control word 2 register? on page 9-37 section 9.4.9, ?ocw3?operational control word 3 register? on page 9-38 i/o register index a-2 82801BA ich2 and 82801BAm ich2-m datasheet master pic icw2 init. cmd word 2 register master pic icw3 init. cmd word 3 register master pic icw4 init. cmd word 4 register master pic ocw1 op ctrl word 1 register 21h section 9.4.3, ?icw2?initialization command word 2 register? on page 9-35 section 9.4.4, ?icw3?master controller initialization command word 3 register? on page 9-35 section 9.4.6, ?icw4?initialization command word 4 register? on page 9-36 section 9.4.7, ?ocw1?operational control word 1 (interrupt mask) register? on page 9-36 aliased at 20h?21h 24h?25h aliased at 20h?21h 28h?29h aliased at 20h?21h 24h?25h aliased at 20h?21h 2ch?2dh aliased at 20h?21h 30h?31h aliased at 20h?21h 34h?35h aliased at 20h?21h 38h?39h aliased at 20h?21h 3ch?3dh counter 0 interval time status byte format counter 0 counter access port register 40h section 9.3.2, ?sbyte_fmt?interval timer status byte format register? on page 9-32 section 9.3.3, ?counter access ports register? on page 9-32 counter 1 interval time status byte format counter 1 counter access port register 41h section 9.3.2, ?sbyte_fmt?interval timer status byte format register? on page 9-32 section 9.3.3, ?counter access ports register? on page 9-32 counter 2 interval time status byte format counter 2 counter access port register 42h section 9.3.2, ?sbyte_fmt?interval timer status byte format register? on page 9-32 section 9.3.3, ?counter access ports register? on page 9-32 timer control word register timer control word register read back counter latch command 43h section 9.3.1, ?tcw?timer control word register? on page 9-30 section 9.3.1.1, ?rdbk_cmd?read back command? on page 9-31 section 9.3.1.2, ?ltch_cmd?counter latch command? on page 9-31 aliased at 40h?43h 50h?53h nmi status and control register 61h section 9.7.1, ?nmi_sc?nmi status and control register? on page 9-51 nmi enable register 70h section 9.7.2, ?nmi_en?nmi enable (and real time clock index)? on page 9-52 real-time clock (standard ram) index register 70h table 9-7 ?rtc (standard) ram bank? on page 9-47 section 9.7.2, ?nmi_en?nmi enable (and real time clock index)? on page 9-52 real-time clock (standard ram) target register 71h table 9-7 ?rtc (standard) ram bank? on page 9-47 extended ram index register 72h extended ram target register 73h table a-1. ich2 fixed i/o registers (continued) register name port eds section and location 82801BA ich2 and 82801BAm ich2-m datasheet a-3 i/o register index aliased at 70h?71h 74h?75h aliased if u128e bit in rtc configuration register is enabled section 9.1.24, ?rtc_conf?rtc configuration register (lpc i/f?d31:f0)? on page 9-14 aliased at 72h?73h or 70h?71h 76h?77h aliased to 70h?71h if u128e bit in rtc configuration register is enabled section 9.1.24, ?rtc_conf?rtc configuration register (lpc i/f?d31:f0)? on page 9-14 channel 2 dma memory low page register 81h section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 channel 3 dma memory low page register 82h section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 channel 1 dma memory low page register 83h section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 reserved page registers 84h?86h channel 0 dma memory low page register 87h section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 reserved page register 88h channel 6 dma memory low page register 89h section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 channel 7 dma memory low page register 8ah section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 channel 5 dma memory low page register 8bh section 9.2.3, ?dmamem_lp?dma memory low page registers? on page 9-25 reserved page registers 8ch?8eh refresh low page register 8fh aliased at 81h?8fh 91h?9fh (except 92h) fast a20 and init register 92h section 9.7.3, ?port92?fast a20 and init register? on page 9-52 slave pic icw1 init. cmd word 1 register slave pic ocw2 op ctrl word 2 register slave pic ocw3 op ctrl word 3 register a0h section 9.4.2, ?icw1?initialization command word 1 register? on page 9-34 section 9.4.8, ?ocw2?operational control word 2 register? on page 9-37 section 9.4.9, ?ocw3?operational control word 3 register? on page 9-38 slave pic icw2 init. cmd word 2 register slave pic icw3 init. cmd word 3 register slave pic icw4 init. cmd word 4 register slave pic ocw1 op ctrl word 1 register a1 section 9.4.3, ?icw2?initialization command word 2 register? on page 9-35 section 9.4.4, ?icw3?master controller initialization command word 3 register? on page 9-35 section 9.4.6, ?icw4?initialization command word 4 register? on page 9-36 section 9.4.7, ?ocw1?operational control word 1 (interrupt mask) register? on page 9-36 aliased at a0h?a1h a4h?a5h aliased at a0h?a1h a8h?a9h aliased at a0h?a1h ach?adh aliased at a0h?a1h b0h?b1h table a-1. ich2 fixed i/o registers (continued) register name port eds section and location i/o register index a-4 82801BA ich2 and 82801BAm ich2-m datasheet advanced power management control port register b2h section 9.8.2.1, ?apm_cnt?advanced power management control port register? on page 9-60 advanced power management status port register b3h section 9.8.2.2, ?apm_sts?advanced power management status port register? on page 9-60 aliased at a0h?a1h b4h?b5h aliased at a0h?a1h b8h?b9h aliased at a0h?a1h bch?bdh channel 4 dma base & current address register c0h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 aliased at c0h c1h channel 4 dma base & current count register c2h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 aliased at c2h c3h channel 5 dma base & current address register c4h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 aliased at c4h c5h channel 5 dma base & current count register c6h section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 aliased at c6h c7h channel 6 dma base & current address register c8h section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 aliased at c8h c9h channel 6 dma base & current count register cah section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 aliased at cah cbh channel 7 dma base & current address register cch section 9.2.1, ?dmabase_ca?dma base and current address registers? on page 9-24 aliased at cch cdh channel 7 dma base & current count register ceh section 9.2.2, ?dmabase_cc?dma base and current count registers? on page 9-25 aliased at ceh cfh channel 4?7 dma command register channel 4?7 dma status register d0h section 9.2.4, ?dmacmd?dma command register? on page 9-26 section 9.2.5, ?dmasts?dma status register? on page 9-26 aliased at d0h d1h channel 4?7 dma write single mask register d4h section 9.2.6, ?dma_wrsmsk?dma write single mask register? on page 9-27 aliased at d4h d5h channel 4?7 dma channel mode register d6h section 9.2.7, ?dmach_mode?dma channel mode register? on page 9-27 aliased at d6h d7h channel 4?7 dma clear byte pointer register d8h section 9.2.8, ?dma clear byte pointer register? on page 9-28 aliased at d8h d9h table a-1. ich2 fixed i/o registers (continued) register name port eds section and location 82801BA ich2 and 82801BAm ich2-m datasheet a-5 i/o register index note: when the pos_dec_en bit is set, additional i/o ports get positively decoded by the ich2. refer to through for a listing of these ranges. channel 4?7 dma master clear register dah section 9.2.9, ?dma master clear register? on page 9-28 aliased at dah dbh channel 4?7 dma clear mask register dch section 9.2.10, ?dma_clmsk?dma clear mask register? on page 9-28 aliased at dch deh channel 4?7 dma write all mask register deh section 9.2.11, ?dma_wrmsk?dma write all mask register? on page 9-29 aliased at deh dfh coprocessor error reigster f0h section 9.7.4, ?coproc_err?coprocessor error register? on page 9-52 pio mode command block offset for secondary drive 170h?177h see ata specification for detailed register description pio mode command block offset for primary drive 1f0h?1f7h see ata specification for detailed register description pio mode control block offset for secondary drive 376h see ata specification for detailed register description pio mode control block offset for primary drive 3f6h see ata specification for detailed register description master pic edge/level triggered register 4d0h section 9.4.10, ?elcr1?master controller edge/level triggered register? on page 9-39 slave pic edge/level triggered register 4d1h section 9.4.11, ?elcr2?slave controller edge/level triggered register? on page 9-40 reset control register cf9h section 9.7.5, ?rst_cnt?reset control register? on page 9-53 table a-1. ich2 fixed i/o registers (continued) register name port eds section and location i/o register index a-6 82801BA ich2 and 82801BAm ich2-m datasheet table a-2. ich2 variable i/o registers register name offset eds section and location lan control/status registers (csr) may be mapped to either i/o space or memory space. lan csr at csr_io_base + offset or csr_mem_base + offset. csr_mem_base set in section 7.1.11, ?csr_mem_base csr?memory-mapped base address register (lan controller? b1:d8:f0)? on page 7-5 csr_io_base set in section 7.1.12, ?csr_io_base?csr i/o-mapped base address register (lan controller?b1:d8:f0)? on page 7-5 scb status word 01h?00h section 7.2.1, ?system control block status word register? on page 7-11 scb command word 03h?02h section 7.2.2, ?system control block command word register? on page 7-12 scb general pointer 07h?04h section 7.2.3, ?system control block general pointer register? on page 7-14 port obh?08h section 7.2.4, ?port register? on page 7-14 eeprom control register 0fh?0eh section 7.2.5, ?eeprom control register? on page 7-15 mdi control register 13h?10h section 7.2.6, ?management data interface (mdi) control register? on page 7-16 receive dma byte count 17h?14h section 7.2.7, ?receive dma byte count register? on page 7-16 early receive interrupt 18h section 7.2.8, ?early receive interrupt register? on page 7-17 flow control register 1ah?19h section 7.2.9, ?flow control register? on page 7-18 pmdr 1bh section 7.2.10, ?power management driver (pmdr) register? on page 7-19 general control 1ch section 7.2.11, ?general control register? on page 7-19 general status 1dh section 7.2.12, ?general status register? on page 7-20 power management i/o registers at pmbase+offset pmbase set in section 9.1.10, ?pmbase?acpi base address (lpc i/f?d31:f0)? on page 9-6 pm1 status 00?01h section 9.8.3.1, ?pm1_sts?power management 1 status register? on page 9-62 pm1 enable 02?03h section 9.8.3.2, ?pm1_en?power management 1 enable register? on page 9-64 pm1 control 04?07h section 9.8.3.3, ?pm1_cnt?power management 1 control register? on page 9-65 pm1 timer 08?0bh section 9.8.3.4, ?pm1_tmr?power management 1 timer register? on page 9-66 processor control 10h?13h section 9.8.3.5, ?proc_cnt?processor control register? on page 9-66 level 2 register 14h section 9.8.3.6, ?lv2?level 2 register? on page 9-67 general purpose event 0 status 28?29h section 9.8.3.9, ?gpe0_sts?general purpose event 0 status register? on page 9-68 general purpose event 0 enables 2a?2bh section 9.8.3.10, ?gpe0_en?general purpose event 0 enables register? on page 9-70 general purpose event 1 status 2c?2d section 9.8.3.11, ?gpe1_sts?general purpose event 1 status register? on page 9-71 general purpose event 1 enables 2e?2f section 9.8.3.12, ?gpe1_en?general purpose event 1 enable register? on page 9-72 82801BA ich2 and 82801BAm ich2-m datasheet a-7 i/o register index smi# control and enable 30?31h section 9.8.3.13, ?smi_en?smi control and enable register? on page 9-72 smi status register 34?35h section 9.8.3.14, ?smi_sts?smi status register? on page 9-74 monitor smi status 40h section 9.8.3.15, ?mon_smi?device monitor smi status and enable register? on page 9-75 device activity status 44h section 9.8.3.16, ?devact_sts?device activity status register? on page 9-76 device trap enable 48h section 9.8.3.17, ?devtrap_en?device trap enable register? on page 9-77 bus address tracker 4ch section 9.8.3.18, ?bus_addr_track?bus address tracker register? on page 9-78 bus cycle tracker 4eh section 9.8.3.19, ?bus_cyc_track?bus cycle tracker register? on page 9-78 tco i/o registers at tcobase + offset tcobase = pmbase + 40h pmbase is set in section 9.1.10, ?pmbase?acpi base address (lpc i/f?d31:f0)? on page 9-6 tco_rld: tco timer reload and current value 00h section 9.9.2, ?tco1_rld?tco timer reload and current value register? on page 9-79 tco_tmr: tco timer initial value 01h section 9.9.3, ?tco1_tmr?tco timer initial value register? on page 9-80 tco_dat_in: tco data in 02h section 9.9.4, ?tco1_dat_in?tco data in register? on page 9-80 tco_dat_out: tco data out 03h section 9.9.5, ?tco1_dat_out?tco data out register? on page 9-80 tco1_sts: tco status 04h?05h section 9.9.6, ?tco1_sts?tco1 status register? on page 9-80 tco2_sts: tco status 06h?07h section 9.9.7, ?tco2_sts?tco2 status register? on page 9-82 tco1_cnt: tco control 08h?09h section 9.9.8, ?tco1_cnt?tco1 control register? on page 9-83 tco2_cnt: tco control 0ah?0bh section 9.9.9, ?tco2_cnt?tco2 control register? on page 9-83 gpio i/o registers at gpiobase + offset gpiobase is set in section 9.1.14, ?gpiobase?gpio base address (lpc i/f?d31:f0)? on page 9-8 gpio use select 00?03h section 9.10.2, ?gpio_use_sel?gpio use select register? on page 9-87 gpio input/output select 04?07h section 9.10.3, ?gp_io_sel?gpio input/output select register? on page 9-88 gpio level for input or output 0c?0fh section 9.10.4, ?gp_lvl?gpio level for input or output register? on page 9-89 gpio blink enable 18?1bh section 9.10.5, ?gpo_blink?gpo blink enable register? on page 9-90 gpio signal invert 2c?2fh section 9.10.6, ?gpi_inv?gpio signal invert register? on page 9-91 table a-2. ich2 variable i/o registers (continued) register name offset eds section and location i/o register index a-8 82801BA ich2 and 82801BAm ich2-m datasheet bmide i/o registers at bm_base + offset bm_base is set at section 10.1.10, ?bm_base?bus master base address register (ide?d31:f1)? on page 10-4 command register primary 00h section 10.2.1, ?bmic[p,s]?bus master ide command register? on page 10-11 status register primary 02h section 10.2.2, ?bmis[p,s]?bus master ide status register? on page 10-12 descriptor table pointer primary 04h?07h section 10.2.3, ?bmid[p,s]?bus master ide descriptor table pointer register? on page 10-12 command register secondary 08h section 10.2.1, ?bmic[p,s]?bus master ide command register? on page 10-11 status register secondary 0ah section 10.2.2, ?bmis[p,s]?bus master ide status register? on page 10-12 descriptor table pointer secondary 0ch?0fh section 10.2.3, ?bmid[p,s]?bus master ide descriptor table pointer register? on page 10-12 usb i/o registers at base address + offset usb base address is set at section 11.1.9, ?base?base address register (usb?d31:f2/f4)? on page 11-4 usb command register 00h?01h section 11.2.1, ?usbcmd?usb command register? on page 11-8 usb status register 02h?03h section 11.2.2, ?usbsta?usb status register? on page 11-11 usb interrupt enable 04h?05h section 11.2.3, ?usbintr?interrupt enable register? on page 11-12 usb frame number 06h?07h section 11.2.4, ?frnum?frame number register? on page 11-12 usb frame list base address 08h?0bh section 11.2.5, ?frbaseadd?frame list base address? on page 11-13 usb start of frame modify 0ch section 11.2.6, ?sofmod?start of frame modify register? on page 11-13 port 0, 2 status/control 10h?11h section 11.2.7, ?portsc[0,1]?port status and control register? on page 11-14 port 1, 3 status/control 12h?13h section 11.2.7, ?portsc[0,1]?port status and control register? on page 11-14 loop back test data 18h smbus i/o registers at smb_base + offset smb_base is set at section 12.1.9, ?smb_base?smbus base address register (smbus?d31:f3)? on page 12-4 host status 00h section 12.2.1, ?hst_sts?host status register? on page 12-7 host control 02h section 12.2.2, ?hst_cnt?host control register? on page 12-8 host command 03h section 12.2.3, ?hst_cmd?host command register? on page 12-9 transmit slave address 04h section 12.2.4, ?xmit_slva?transmit slave address register? on page 12-9 host data 0 05h section 12.2.5, ?hst_d0?data 0 register? on page 12-9 host data 1 06h section 12.2.6, ?hst_d1?data 1 register? on page 12-9 table a-2. ich2 variable i/o registers (continued) register name offset eds section and location 82801BA ich2 and 82801BAm ich2-m datasheet a-9 i/o register index block data byte 07h section 12.2.7, ?block_db?block data byte register? on page 12-10 receive slave address 09h section 12.2.8, ?rcv_slva?receive slave address register? on page 12-10 receive slave data 0ah section 12.2.9, ?slv_data?receive slave data register? on page 12-10 ac?97 audio i/o registers at nambar + offset nambar is set at section 13.1.11, ?nabmbar?native audio bus mastering base address register (audio?d31:f5)? on page 13-5 pcm in buffer descriptor list base address register 00h section 13.2.1, ?x_bdbar?buffer descriptor base address register? on page 13-9 pcm in current index value 04h section 13.2.2, ?x_civ?current index value register? on page 13-10 pcm in last valid index 05h section 13.2.3, ?x_lvi?last valid index register? on page 13-10 pcm in status register 06h section 13.2.4, ?x_sr?status register? on page 13-11 pcm in position in current buffer 08h section 13.2.5, ?x_picb?position in current buffer register? on page 13-12 pcm in prefetched index value 0ah section 13.2.6, ?x_piv?prefetched index value register? on page 13-12 pcm in control register 0bh section 13.2.7, ?x_cr?control register? on page 13-13 pcm out buffer descriptor list base address register 10h section 13.2.1, ?x_bdbar?buffer descriptor base address register? on page 13-9 pcm out current index value 14h section 13.2.2, ?x_civ?current index value register? on page 13-10 pcm out last valid index 15h section 13.2.3, ?x_lvi?last valid index register? on page 13-10 pcm out status register 16h section 13.2.4, ?x_sr?status register? on page 13-11 pcm out position in current buffer 18h section 13.2.5, ?x_picb?position in current buffer register? on page 13-12 pcm out prefetched index value 1ah section 13.2.6, ?x_piv?prefetched index value register? on page 13-12 pcm out control register 1bh section 13.2.7, ?x_cr?control register? on page 13-13 mic. in buffer descriptor list base address register 20h section 13.2.1, ?x_bdbar?buffer descriptor base address register? on page 13-9 mic. in current index value 24h section 13.2.2, ?x_civ?current index value register? on page 13-10 mic. in last valid index 25h section 13.2.3, ?x_lvi?last valid index register? on page 13-10 mic. in status register 26h section 13.2.4, ?x_sr?status register? on page 13-11 mic in position in current buffer 28h section 13.2.5, ?x_picb?position in current buffer register? on page 13-12 mic. in prefetched index value 2ah section 13.2.6, ?x_piv?prefetched index value register? on page 13-12 mic. in control register 2bh section 13.2.7, ?x_cr?control register? on page 13-13 table a-2. ich2 variable i/o registers (continued) register name offset eds section and location i/o register index a-10 82801BA ich2 and 82801BAm ich2-m datasheet global control 2ch section 13.2.8, ?glob_cnt?global control register? on page 13-14 global status 30h section 13.2.9, ?glob_sta?global status register? on page 13-15 codec access semaphore register 34h section 13.2.10, ?cas?codec access semaphore register? on page 13-16 ac?97 modem i/o registers at mbar + offset mbar is set in section 14.1.11, ?mbar?modem base address register (modem?d31:f6)? on page 14-5 modem in buffer descriptor list base address register 00h section 14.2.1, ?x_bdbar?buffer descriptor list base address register? on page 14-8 modem in current index value register 04h section 14.2.2, ?x_civ?current index value register? on page 14-9 modem in last valid index register 05h section 14.2.3, ?x_lvi?last valid index register? on page 14-9 modem in status register 06h section 14.2.4, ?x_sr?status register? on page 14-10 modem in position in current buffer register 08h section 14.2.5, ?x_picb?position in current buffer register? on page 14-11 modem in prefetch index value register 0ah section 14.2.6, ?x_piv?prefetch index value register? on page 14-11 modem in control register 0bh section 14.2.7, ?x_cr?control register? on page 14-11 modem out buffer descriptor list base address register 10h section 14.2.1, ?x_bdbar?buffer descriptor list base address register? on page 14-8 modem out current index value register 14h section 14.2.2, ?x_civ?current index value register? on page 14-9 modem out last valid register 15h section 14.2.3, ?x_lvi?last valid index register? on page 14-9 modem out status register 16h section 14.2.4, ?x_sr?status register? on page 14-10 modem in position in current buffer register 18h section 14.2.5, ?x_picb?position in current buffer register? on page 14-11 modem out prefetched index register 1ah section 14.2.6, ?x_piv?prefetch index value register? on page 14-11 modem out control register 1bh section 14.2.7, ?x_cr?control register? on page 14-11 global control 3ch section 14.2.8, ?glob_cnt?global control register? on page 14-12 global status 40h section 14.2.9, ?glob_sta?global status register? on page 14-13 codec access semaphore register 44h section 14.2.10, ?cas?codec access semaphore register? on page 14-14 table a-2. ich2 variable i/o registers (continued) register name offset eds section and location 82801BA ich2 and 82801BAm ich2-m datasheet index-1 register bit index b numerics 4 channel capability 13-15, 14-13 6 channel capability 13-15, 14-13 a a20gate pass-through enable (a20passen) 11-6 ac ?97 cold reset# 13-14 ac ?97 interrupt routing 14-6 ac ?97 interrupt routing 13-7 ac?97 cold reset# 14-12 ac?97 warm reset 13-14, 14-12 ac97_en 9-66 ac97_sts 9-65 aclink shut off 13-14, 14-12 acpi_en 9-6 ad3 13-15, 14-13 address 12-8 address increment/decrement select 9-27 adlib_act_sts 9-72 adlib_lpc_en 9-18 adlib_trp_en 9-73 af alarm flag 9-50 afterg3_en 9-55 aie alarm interrupt enable 9-49 alt_a20_gate 9-52 altacc_en alternate access mode enable 9-12 apic data 9-42 apic id 9-43 apic index 9-41 apic_en 9-12 apm_sts 9-71 apmc_en 9-69 audio_act_sts 9-72 audio_trp_en 9-73 autoinitialize enable 9-27 automatic end of interrupt (aeoi) 9-36 auxiliary current 7-8 b base address 7-5, 9-6, 9-8, 10-4, 11-4, 11-13, 12-3, 13-5, 14-5 base address of descriptor table (baddr) 10-12 base and current address 9-24 base and current count 9-25 base class code 7-4, 8-5, 9-5, 10-4, 11-4, 12-3, 13-4 base class code value 14-4 binary/bcd countdown select 9-30 bios_en 9-69 bios_rls bios release 9-69 bios_sts 9-71 bioswe bios write enable 9-7 bioswr_sts 9-77 bit 1 of slot 12 13-15, 14-13 bit 2 of slot 12 13-15, 14-13 bit 3 of slot 12 13-15, 14-13 ble bios lock enable 9-7 block data byte 12-9 boot_sts 9-78 buffer completion interrupt status (bcis) 13-11, 14-10 buffer descriptor base address 13-9 buffer descriptor list base address 14-8 buffered mode (buf) 9-36 bus master enable (bme) 7-2, 8-3, 10-2, 11-2, 13-2, 14-2 bus master ide active (act) 10-12 bus_err 12-6 byte_done_sts 12-6 c cap_id capability id 7-8 cap_list capabilities list 7-3 cap_ptr capabilities pointer 7-6 cascaded interrupt controller irq connection 9-35 channel 0 select 9-11 register bit index index-2 82801BA ich2 and 82801BAm ich2-m datasheet channel 1 select 9-11 channel 2 select. 9-11 channel 3 select 9-11 channel 5 select 9-11 channel 6 select 9-11 channel 7 select 9-11 channel mask bits 9-29 channel mask select 9-27 channel request status 9-26 channel terminal count status 9-26 clear byte pointer 9-28 clear mask register 9-28 cls cache line size 7-4 cna cu not active 7-11 cna mask 7-12 cnf1_lpc_en 9-17 cnf2_lpc_en 9-17 codec write in progress (cwip) 13-16 coma decode range 9-14 coma_lpc_en 9-18 comb decode range 9-14 comb_lpc_en 9-18 configure flag (cf) 11-9 connect status change 11-15 copr_err_en coprocessor error enable 9-11 coproc_err 9-52 count register status 9-32 countdown type status 9-32 counter 0 select 9-31 counter 1 select 9-31 counter 2 select 9-31 counter latch command 9-31 counter mode selection 9-30 counter out pin state 9-32 counter port 9-32 counter select 9-30 counter selection 9-31 cpu_bist_en 9-13 cpupwr_flr cpu power failure 9-55 cpuslp_en 9-54 cuc command unit command 7-13 current connect status 11-15 current equals last valid (celv) 13-11, 14-10 current index value 13-10, 14-9 cus command unit status 7-11 cx command unit (cu) executed 7-11 cx mask 7-12 d d1 support 7-8 d2 support 7-8 data 7-16 data parity error detected (dpd) 7-3, 8-4, 8-8 data scale 7-9 data select 7-9 data_msg0 data message byte 0 12-9 data_msg1 data message byte 1 12-9 data0/count 12-8 data1 12-8 date alarm 9-50 dcb_en dma collection buffer enable 9-12 deep power-down on link down enable 7-19 delivery mode 9-46 delivery status 9-45 destination 9-45 destination mode 9-45 detected parity error (dpe) 7-3, 8-4, 8-8 dev_err 12-6 dev_sts devsel# timing status 9-4 dev_trap_en 9-71 dev_trap_sts 9-71 device id value 9-2, 11-2, 13-2, 14-2 device id value 12-1 device identification number 7-2, 8-2 device specific initialization (dsi) 7-8 devmon_sts device monitor status 9-70 devsel# timing status (devt) 10-3, 11-3, 12-2, 13-3 dm data mode 9-49 dma channel group enable 9-26 dma channel select 9-27 dma controller halted (dch) 13-11, 14-10 dma group arbitration priority 9-26 dma low page 9-25 82801BA ich2 and 82801BAm ich2-m datasheet index-3 register bit index dma transfer mode 9-27 dma transfer type 9-27 dpe detected parity error 9-4 dped data parity error detected 9-4 drive 0 dma capable 10-12 drive 0 dma timing enable (dte0) 10-6 drive 0 fast timing bank (time0) 10-7 drive 0 iordy sample point enable (ie0) 10-7 drive 0 prefetch/posting enable (ppe0) 10-7 drive 1 dma capable 10-12 drive 1 dma timing enable (dte1) 10-6 drive 1 fast timing bank (time1) 10-6 drive 1 iordy sample point enable (ie1) 10-6 drive 1 prefetch/posting enable (ppe1) 10-6 drive 1 timing register enable (sitre) 10-6 dse daylight savings enable 9-49 dt delivery type 9-44 dte delayed transaction enable 9-12 duplex mode 7-20 dv division chain select 9-48 dynamic data 7-9 e early receive count 7-17 edge/level bank select (ltim) 9-34 eecs eeprom chip select 7-15 eedi eeprom serial data in 7-15 eedo eeprom serial data out 7-15 eesk eeprom serial clock 7-15 enable special mask mode (esmm) 9-38 enter global suspend mode (egsm) 11-9 eos end of smi 9-69 er early receive 7-11 er mask 7-12 error 10-12 f f1_disable 9-22 f2_disable 9-22 f3_disable 9-22 f4_disable 9-22 f5_disable 9-22 f6_disable 9-22 failed 12-6 fast_pcb0 fast primary drive 0 base clock 10-10 fast_pcb1 fast primary drive 1 base clock 10-9 fast_scb0 fast secondary drive 0 base clock 10-9 fast_scb1 fast secondary drive 1 base clock 10-9 fc full 7-18 fc paused 7-18 fc paused low 7-18 fcp flow control pause 7-11 fcp mask 7-12 fdd decode range 9-15 fdd_lpc_en 9-18 fifo error (fifoe) 13-11, 14-10 fifo error interrupt enable (feie) 13-13, 14-11 flow control threshold 7-18 force global resume (fgr) 11-9 force_thtl 9-63 fr frame received 7-11 fr mask 7-12 frame list current index/frame number 11-12 freq_strap 9-13 full_rst 9-53 fwh_c0_en 9-16, 9-21 fwh_c0_idsel 9-19 fwh_c8_en 9-16, 9-21 fwh_c8_idsel 9-19 fwh_d0_en 9-16, 9-21 fwh_d0_idsel 9-19 fwh_d8_en 9-16, 9-21 fwh_d8_idsel 9-19, 9-20 fwh_e0_en 9-16 fwh_e0_idsel 9-19, 9-20 fwh_e8_en 9-16 fwh_e8_idsel 9-19, 9-20 fwh_f0_en 9-16 fwh_f0_idsel 9-19, 9-20 fwh_f8_en 9-16 fwh_f8_idsel 9-19 register bit index index-4 82801BA ich2 and 82801BAm ich2-m datasheet g gameh_lpc_en 9-17 gamel_lpc_en 9-17 gbl _sts 9-61 gbl_en 9-61 gbl_rls global release 9-62 gbl_smi_en 9-69 gen1_base generic i/o decode range 1 base 9-17 gen1_en generic decode range 1 enable 9-17 gen2_base generic i/o decode range 2 base 9-20 gen2_en generic i/o decode range 2 en- able 9-20 global reset (greset) 11-9 gpe0_sts 9-70 gpe1_sts 9-70 gpi interrupt enable (gie) 13-14, 14-12 gpi route 9-56 gpi status change interrupt (gsci) 13-16, 14-14 gpi_en 9-68 gpi_sts 9-67 gpio_en 9-8 gpio_sel 9-84 gpio_use_sel 9-83 h hchalted 11-11 header type 7-5, 9-5 header type value 13-4 header value 14-4 hide_isa hide isa bridge 9-11 hole enable (15mb-16mb). 8-12 host controller process error 11-11 host controller reset (hcreset) 11-9 host system error 11-11 host_busy 12-6 hourform hour format 9-49 hp_pci_en 8-12 hst_en smbus host enable 12-4 hubnmi_sts 9-76 hubsci_sts 9-77 hubserr_sts 9-76 hubsmi_sts 9-77 i i/o address base bits 8-7 i/o address limit bits 8-7 i/o addressing capability 8-7 i/o apic identification 9-44 i/o space (ios) 14-2 i/o space enable (ioe) 7-2, 8-3 i/o space enable (iose) 11-2, 12-2 i2c_en 12-4 ia64_en ia64 processor mode enable 9-54 icw/ocw select 9-34 icw4 write required (ic4) 9-34 ide decode enable (ide) 10-6 idep0_act_sts 9-73 idep0_trp_en 9-73 idep1_act_sts 9-73 idep1_trp_en 9-73 ides0_act_sts 9-72 ides0_trp_en 9-73 ides1_act_sts 9-72 ides1_trp_en 9-73 init_now 9-52 int_ln interrupt line 7-7 int_pn interrupt pin 7-7 interesting packet 7-19 internal lan master request status (lan_mreq_sts) 8-13 internal pci master request status (int_mreq_sts) 8-13 interrupt 10-12 interrupt enable 7-16 interrupt input pin polarity 9-45 interrupt level select (l2, l1, l0) 9-37 interrupt line 11-5, 13-6, 14-6 interrupt line 12-4 interrupt on complete (ioc) enable 11-12 interrupt on completion enable (ioce) 13-13, 14-11 interrupt pin 12-4 interrupt pin 11-5 interrupt request level 9-35 interrupt request mask 9-36 82801BA ich2 and 82801BAm ich2-m datasheet index-5 register bit index interrupt vector base address 9-35 intr 12-6 intrd_det intruder detect 9-78 intrd_sel 9-80 intren 12-7 inuse_sts 12-6 io space indicator 12-3 iochk_nmi_en 9-51 iochk_nmi_sts iochk# nmi source status 9-51 iordy sample point (isp) 10-6 ios (i/o space) 13-2 iose i/o space enable (iose) 10-2 irq number 9-42 irq routing 9-8, 9-9 irq10 ecl 9-40 irq11 ecl 9-40 irq12 ecl 9-40 irq12len mouse irq12 latch enable 9-12 irq14 ecl 9-40 irq15 ecl 9-40 irq1len keyboard irq1 latch enable 9-11 irq3 ecl 9-39 irq4 ecl 9-39 irq5 ecl 9-39 irq6 ecl 9-39 irq7 ecl 9-39 irq9 ecl 9-40 irqen interrupt routing enable 9-8, 9-9 irqf interrupt request flag 9-50 isa enable 8-11 k kbc_act_sts 9-72 kbc_lpc_en 9-17 kbc_trp_en 9-73 kill 12-7 l l128lock lower 128-byte lock 9-14 lan connect address 7-16 lan connect register address 7-16 lan connect software reset 7-19 last valid buffer completion interrupt (lvbci) 13-11, 14-10 last valid buffer interrupt enable (lvbie) 13-13, 14-11 last valid index 13-10, 14-9 latch count of selected counters 9-31 latch status of selected counters 9-31 leg_act_sts 9-72 leg_io_trp_en 9-73 legacy_usb_en 9-69 legacy_usb_sts 9-71 line status 11-14 link status change indication 7-19 link status indication 7-20 loop back test mode 11-8 low speed device attached (ls) 11-14 lpt decode range 9-15 lpt_lpc_en 9-18 m m interrupt mask 7-12 magic packet 7-19 mas (master-abort status) 14-3 mask 9-45 master abort mode 8-11 master clear 9-28 master latency count 8-6 master/slave in buffered mode 9-36 master-abort status (mas) 13-3 max packet (maxp) 11-9 maximum redirection entries 9-44 mc_lpc_en 9-17 mcsmi_en microcontroller smi enable 9-68 mcsmi_sts microcontroller smi# status 9-70 md3 13-15, 14-13 mdi management data interrupt 7-11 memory address base 8-9 memory address limit 8-9 memory space enable (mse) 7-2, 8-3 mic in interrupt (mint) 13-15, 14-13 microprocessor mode 9-36 midi decode range 9-15 midi_act_sts 9-72 midi_lpc_en 9-18 midi_trp_en 9-73 register bit index index-6 82801BA ich2 and 82801BAm ich2-m datasheet mltc master latency timer count 7-4 mode selection status 9-32 modem in interrupt (miint) 13-16, 14-14 modem out interrupt (moint) 13-16, 14-14 mon_trap_base 9-57 mon4_fwd_en 9-56 mon4_mask 9-57 mon5_fwd_en 9-56 mon5_mask 9-57 mon6_fwd_en 9-56 mon6_mask 9-57 mon7_fwd_en 9-56 mon7_mask 9-57 mss decode range 9-15 mss_lpc_en 9-18 multi-function device 9-5 multi-function device. 7-5 multi-transaction timer count value 8-12 mwie memory write and invalidate enable 7-2 n newcentury_sts 9-77 nmi_en 9-52 nmi_now 9-79 nmi2smi_en 9-77, 9-79 no_reboot 9-13 nxt_ptr next item pointer 7-8 o ocw2 select 9-37 ocw3 select 9-38 opcode 7-16 overcurrent active 11-14 overcurrent indicator 11-14 p parity error response 8-3 parity error response enable 8-11 pass through state (pstate) 11-6 pcb0 10-10 pcb1 10-10 pci interrupt enable (usbpirqen) 11-6 pci master request status (pci_mreq_sts) 8-13 pci_dac_en 8-11 pci_serr_en 9-51 pcm 4/6 enable 13-14 pcm in interrupt (piint) 13-16, 14-14 pcm out interrupt (point) 13-16, 14-13 per parity error response 7-2, 9-3 per_smi_sel 9-54 periodic_en 9-68 periodic_sts 9-70 pf periodic interrupt flag 9-50 pie periodic interrupt enable 9-49 pirqae_act_sts 9-72 pirqbf_act_sts 9-72 pirqcg_act_sts 9-72 pirqdh_act_sts 9-72 pm1_sts_reg 9-70 pme clock 7-8 pme enable 7-9 pme status 7-9, 7-19 pme support 7-8 pme_en 9-66 pme_sts 9-64 pointer field 7-14 poll mode command 9-38 port enable/disable change 11-15 port enabled/disabled (port_en) 11-15 port function selection 7-14 port reset 11-14 port0en 11-7 port1en 11-7 pos_dec_en positive decode enable 9-12 position in current buffer 13-12, 14-11 power state 7-9 prbtnor_sts power button override status 9-60 prefetchable memory address base 8-9 prefetchable memory address limit 8-10 prefetched index value 13-12 prefetched index value 14-11 prim_sig_mode 10-9 primany resume interrupt enable 13-14, 14-12 primary bus number 8-6 primary codec ready (pcr) 13-15, 14-13 primary drive 0 cycle time (pct0) 10-9 82801BA ich2 and 82801BAm ich2-m datasheet index-7 register bit index primary drive 0 synchronous dma mode enable (psde0) 10-8 primary drive 1 cycle time (pct1) 10-9 primary drive 1 iordy sample point (pisp1) 10-7 primary drive 1 recovery time (prct1) 10-7 primary drive 1 synchronous dma mode enable (psde1) 10-8 primary master channel cable reporting 10-10 primary resume interrupt 13-15, 14-13 primary slave channel cable reporting 10-10 programming interface value 10-3, 14-3 prq 9-44 pwr_flr power failure 9-55 pwrbtn__sts 9-60 pwrbtn_en 9-61 pwrbtn_lvl 9-54 pwrok_flr pwrok failure 9-55 r read / write control (rwc) 10-11 read back command 9-31 read completion status 13-15 read/write select 9-30 read/write selection status 9-32 ready 7-16 receive dma byte count 7-16 received master abort (rma) 8-4, 8-8 received master-abort status (rma) 10-3, 11-3 received system error (sse) 8-4, 8-8 received target abort (rta) 7-3, 8-4, 8-8 recovery time (rct) 10-6 redirection entry clear 9-43 ref_toggle refresh cycle toggle 9-51 register read command 9-38 remote irr 9-45 reset registers(rr) 14-11 reset registers(rr). 13-13 resource indicator 9-6, 9-8 resource type indicator (rte) 10-4, 11-4, 13-5, 14-5 resume detect (rsm_det) 11-11, 11-14 resume interrupt enable 11-12 revision id value 13-3, 14-3 revision identification number 8-4, 9-4 revision identification number. 7-3 ri_en 9-66 ri_sts 9-64 rma master abort status 7-3, 9-4 rnr mask 7-12 rnr receive not ready 7-11 rotate and eoi codes (r, sl, eoi) 9-37 rs rate select 9-48 rst_cpu 9-53 rta received target abort 9-4 rtc_en rtc event enable 9-61 rtc_indx real time clock index address 9-52 rtc_pwr_sts 9-55 rtc_sts 9-60 ruc receive unit command 7-13 run/pause bus master (rpbm) 13-13, 14-11 run/stop (rs) 11-10 rus receive unit status 7-11 rw 12-8 s safe_mode 9-13 sb16 decode range 9-15 sb16_lpc_en 9-18 scb general pointer 7-14 scb1 10-10 scbo 10-10 sci_en 9-62 sci_irq_sel 9-6 sec_sig_mode 10-9 second_to_sts 9-78 secondary bus number 8-6 secondary codec ready (scr) 13-15, 14-13 secondary drive 0 cycle time (sct0) 10-8 secondary drive 0 synchronous dma mode enable (ssde0) 10-8 secondary drive 1 cycle time (sct1) 10-8 secondary drive 1 iordy sample point (sisp1) 10-7 secondary drive 1 recovery time (srct1) 10-7 register bit index index-8 82801BA ich2 and 82801BAm ich2-m datasheet secondary drive 1 synchronous dma mode enable (ssde1) 10-8 secondary master channel cable reporting 10-10 secondary resume interrupt 13-15, 14-13 secondary resume interrupt enable 13-14, 14-12 secondary slave channel cable reporting 10-10 sendnow 9-79 serial bus release number 11-5 serirq_smi_sts 9-70 serr# due to delayed transaction timeout (serr_dtt). 8-14 serr# due to received target abort (serr_rta). 8-14 serr# enable 8-11 serr# enable (serr_en) 7-2, 8-3 serr# enable on delayed transaction timeout (serr_dtt_en) 8-13 serr# enable on receiving target abort (serr_rta_en) 8-13 serr#_nmi_sts serr# nmi source status 9-51 serr_dtt serr# due to delayed transaction timeout 9-10 serr_dtt_en serr# on delayed transac- tion timeout enable 9-10 serr_en 9-3 serr_rta serr# due to received target abort 9-10 serr_rta_en serr# on received target abort enable 9-10 set update cycle inhibit 9-49 sfpw start frame pulse width 9-9 short packet interrupt enable 11-12 si software generated interrupt 7-12 signaled system error (sse) 7-3 signaled target abort (sta) 8-4 signaled target-abort status 12-2 signaled target-abort status (sta) 10-3, 11-3 single or cascade (sngl) 9-34 sirqen serial irq enable 9-9 sirqmd serial irq mode select 9-9 sirqsz serial irq frame size 9-9 slave identification code 9-36 slave_addr 12-9 slp_en 9-62 slp_smi_en 9-69 slp_smi_sts 9-71 slp_typ 9-62 smb_cmd 12-7 smb_for_bios 9-22 smb_smi_en 12-4 smb_wak_sts smbus wake status 9-64 smbalert_sts 12-6 smbus_smi_sts 9-70 smi at end of pass-through enable (smiatendps) 11-6 smi caused by end of pass-through (smibyendps) 11-6 smi caused by port 60 read (trapby60r) 11-6 smi caused by port 60 write (trapby60w) 11-6 smi caused by port 64 read (trapby64r) 11-6 smi caused by port 64 write (trapby64w) 11-6 smi caused by usb interrupt (smibyusb) 11-6 smi on port 60 reads enable (60ren) 11-7 smi on port 60 writes enable (60wen) 11-7 smi on port 64 reads enable (64ren) 11-7 smi on port 64 writes enable (64wen) 11-7 smi on usb irq (usbsmien) 11-7 sof timing value 11-13 software debug (swdbg) 11-9 special fully nested mode (sfnm) 9-36 special mask mode (smm) 9-38 speed 7-20 spkr_dat_en 9-51 sqwe square wave enable 9-49 sse signaled system error 9-4 sta signaled target abort 9-4 start 12-7 start/stop bus master (start) 10-11 82801BA ich2 and 82801BAm ich2-m datasheet index-9 register bit index sub class code 10-3, 11-4, 12-3, 13-4 sub class code value 14-4 sub-class code 7-4, 8-5, 9-5 subordinate bus number 8-6 subsystem id value 13-6, 14-6 subsystem vendor id value 13-6, 14-5 suspend 11-14 sw_tco_smi 9-77 swi software interrupt 7-11 swsmi_rate_sel 9-54 swsmi_tmr_en software smi# timer enable 9-69 swsmi_tmr_sts 9-71 sys_rst 9-53 t tco_en 9-68 tco_int_en tco interrupt enable 9-7 tco_int_sel tco interrupt select 9-7 tco_int_sts 9-77 tco_message 9-80 tco_sts 9-70 tco_tmr_hlt tco timer halt 9-79 tcosci_en 9-66 tcosci_sts 9-64 thrm#_pol 9-66 thrm_dty 9-63 thrm_en 9-66 thrm_sts thermal interrupt status 9-65 thrmor_sts thermal interrupt override status 9-65 tht_en 9-63 thtl_dty 9-63 thtl_sts throttle status 9-63 tim_cnt2_en timer counter 2 enable 9-51 timeout 9-77 timeout/crc interrupt enable 11-12 tmr_val 9-62 tmr2_out_sts timer counter 2 out status 9-51 tmrof_en timer overflow interrupt enable 9-61 tmrof_sts timer overflow status 9-61 top_swap 9-13 trigger mode 9-45 u u128e upper 128-byte enable 9-14 u128lock upper 128-byte lock 9-14 uf update-ended flag 9-50 uie update-ended interrupt enable 9-49 uip update in progress 9-48 usb error interrupt 11-11 usb interrupt (usbint) 11-11 usb1_en 9-66 usb1_sts 9-65 usb2_en 9-66 usb2_sts 9-65 v vendor id value 9-2, 11-1, 12-1, 13-1, 14-1 vendor identification number 8-2 version 7-8 vga enable 8-11 vrt valid ram and time bit 9-50 w wak_sts 9-60 wdstatus watchdog status 9-80 wr_pingpong_en 10-10 x xoff 7-18 xon 7-18 intel around the world united states and canada intel corporation robert noyce building 2200 mission college boulevard p.o. box 58119 santa clara, ca 95052-8119 usa phone: (800) 628-8686 europe intel corporation (uk) ltd. pipers way swindon wiltshire sn3 1rj uk phone: england (44) 1793 403 000 germany (49) 89 99143 0 france (33) 1 4571 7171 italy (39) 2 575 441 israel (972) 2 589 7111 netherlands (31) 10 286 6111 sweden (46) 8 705 5600 asia-pacific intel semiconductor ltd. 32/f two pacific place 88 queensway, central hong kong, sar phone: (852) 2844 4555 japan intel kabushiki kaisha p.o. box 115 tsukuba-gakuen 5-6 tokodai, tsukuba-shi ibaraki-ken 305 japan phone: (81) 298 47 8522 south america intel semicondutores do brazil rue florida, 1703-2 and cj22 cep 04565-001 sao paulo-sp brazil phone: (55) 11 5505 2296 for more information to learn more about intel corporation, visit our site on the world wide web at www.intel.com |
Price & Availability of 82801BA
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |